CVE-2025-54139: HAX CMS' application pages are vulnerable to clickjacking
Noroxi assessment
Priority: Monitor (action score 24/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.35% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: @haxtheweb/haxcms-nodejs (npm) 11.0.13; elmsln/haxcms (Packagist) 11.0.8.
Low priority for now. Upgrade to @haxtheweb/haxcms-nodejs (npm) 11.0.13; elmsln/haxcms (Packagist) 11.0.8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
HAX CMS allows users to manage their microsite universe with a NodeJS or PHP backend. In haxcms-nodejs versions 11.0.12 and below and in haxcms-php versions 11.0.7 and below, all pages within the HAX CMS application do not contain headers to prevent other websites from loading the site within an iframe. This applies to both the CMS and generated sites. An unauthenticated attacker can load the standalone login page or other sensitive functionality within an iframe, performing a UI redressing attack (clickjacking). This can be used to perform social engineering attacks to attempt to coerce users into performing unintended actions within the HAX CMS application. This is fixed in haxcms-nodejs version 11.0.13 and haxcms-php 11.0.8.
- Published
- Jul 22, 2025
- Updated
- Jun 17, 2026
- EPSS
- 0.3% · 29th percentile
- CWE
- CWE-1021
Report tools
Action score
24
Low priority for now.
- CVSS
- 24 / 40 · 6.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- proof of concept
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 6.1
- CNA · GitHub_M
- 4.3
- 1.8 point gap
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Do you have framing protection?Check security headers
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Do you have framing protection?
Clickjacking protection needs CSP frame-ancestors or X-Frame-Options. Check for free whether your site sends them.
Check security headersVersions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
haxtheweb issues
- < 11.0.13, < 11.0.8affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- psu haxcms-nodejs11.0.6 and later · before 11.0.13
- psu haxcms-php11.0.0 and later · before 11.0.8
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| npm | @haxtheweb/haxcms-nodejs | before 11.0.13 | 11.0.13 |
| Packagist | elmsln/haxcms | before 11.0.8 | 11.0.8 |
Same product
psu: all recordsOther highest-scoring records for the same primary product.
- CVE-2025-54127HAXcms's Insecure Default Configuration Leads to Unauthenticated Access37Monitor
- CVE-2025-49141HaxCMS-PHP Command Injection Vulnerability35Monitor
- CVE-2025-54378HAX CMS Backend Lacks Comprehensive Authorization Checks33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-54134Jul 21, 2025 · HAX CMS NodeJs's Improper Error Handling Leads to Denial of Service28Monitor
- ← EarlierCVE-2025-54137Jul 22, 2025 · NodeJS version of the HAX CMS application is distributed with Default Secrets29Monitor
- Later →CVE-2026-22704Jan 10, 2026 · HAXcms Has Stored XSS Vulnerability that May Lead to Account Takeover21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| npm:@haxtheweb/haxcms-nodejs | 11.0.13 | Package registry (OSV) |
| Packagist:elmsln/haxcms | 11.0.8 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-4913943 days apart@haxtheweb/haxcms-nodejs Iframe Phishing vulnerability26Monitor
Not on record for this CVE: EPSS history · researcher credit · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-1021 · Improper Restriction of Rendered UI Layers or FramesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- ClickjackingCAPEC-103likelihood: Medium · High
- Flash File OverlayCAPEC-181Medium
- iFrame OverlayCAPEC-222likelihood: Medium · High
- Task ImpersonationCAPEC-504likelihood: Medium · High
- TapjackingCAPEC-506likelihood: Low · Low
- Cross Frame Scripting (XFS)CAPEC-587High
- Credential Prompt ImpersonationCAPEC-654likelihood: Medium · High
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.