CVE-2025-54139 json
HAX CMS' application pages are vulnerable to clickjacking
published last yr. modified last mo. also EUVD-2025-22388 , GHSA-54vw-f4xf-f92j
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- npm @haxtheweb/haxcms-nodejs 11.0.13
- packagist elmsln/haxcms 11.0.8
- haxtheweb hax 11.0.8, 11.0.13
- haxtheweb haxcms-nodejs 11.0.13
- psu haxcms-nodejs 11.0.13
- haxtheweb haxcms-php 11.0.8
- psu haxcms-php 11.0.8
Is CVE-2025-54139 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/haxtheweb/issues/security/advisories/GHSA-54vw-f4xf-f92j referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| GitHub | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | @haxtheweb/haxcms-nodejs | <11.0.13 |
11.0.13 |
| packagist | elmsln/haxcms | <11.0.8 |
11.0.8 |
Affected products
- haxtheweb issues
Classification
- Weakness
-
- CWE-1021 Improper Restriction of Rendered UI Layers or Frames
References
-
github.com
/haxtheweb/haxcms-nodejs/commit/777f9a7ff9675a160496f350d766df1f1f9b9b99
web, patch
-
github.com
/haxtheweb/haxcms-php/commit/708dc8518928fe307044e67bff8b0f397cfdd606
web, patch
-
github.com
/haxtheweb/issues/security/advisories/GHSA-54vw-f4xf-f92j
exploit, web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2025-54139
advisory
-
github.com
/haxtheweb/issues
package
Sources
- CVE List CVE-2025-54139
- GitHub Advisory GHSA-54vw-f4xf-f92j
- NVD CVE-2025-54139
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.