VulnerabilityPublished 22 Jul 2025

CVE-2025-54139: haxtheweb issues · Clickjacking

Affects haxtheweb issuesSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 11.0.13 : update haxtheweb issues when convenient.

Data as of 26 Oct 2026, 12:29 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.13, 11.0.8

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Jul 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade haxtheweb/haxcms-nodejs to 11.0.13; haxtheweb/haxcms-php to 11.0.8.

Affected software

Product	Affected	Fixed in
npmhaxtheweb/haxcms-nodejs`pkg:npm/haxtheweb/haxcms-nodejs`Other threats	Affected <11.0.13	Fixed in 11.0.13
Packagisthaxtheweb/haxcms-php`pkg:composer/haxtheweb/haxcms-php`Other threats	Affected <11.0.8	Fixed in 11.0.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade affected HAX CMS installations to haxcms-nodejs version 11.0.13 or later, or haxcms-php version 11.0.8 or later, where the issue is fixed by adding frame-embedding prevention headers. If immediate upgrade is not feasible, organizations can implement web server or reverse proxy configurations to add X-Frame-Options: DENY or Content-Security-Policy frame-ancestors directives to all HAX CMS pages and generated microsites to block iframe embedding. Additionally, organizations should conduct user awareness training to recognize and avoid social engineering attempts involving clickjacking. Regular security assessments and penetration testing should include checks for UI redressing vulnerabilities. Monitoring web traffic for suspicious referrer headers or iframe embedding attempts can help detect exploitation attempts. Finally, applying Content Security Policy (CSP) with frame-ancestors restrictions site-wide is a robust defense that should be part of the security posture.

Description

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.

Impact

For European organizations using HAX CMS (NodeJS or PHP versions prior to the fixed releases), this vulnerability could enable attackers to conduct clickjacking attacks that may trick administrators or content managers into performing unintended actions, such as modifying site content, changing configurations, or potentially escalating privileges if combined with other vulnerabilities. While the vulnerability does not directly expose sensitive data or cause service disruption, the integrity of the CMS-managed content and configurations could be compromised. This risk is particularly relevant for organizations relying on HAX CMS for managing multiple microsites or critical web content, including government agencies, educational institutions, and private enterprises. The social engineering aspect means that user training and awareness are also factors in the potential impact. Since the vulnerability is unauthenticated and remotely exploitable, attackers can target users without needing prior access. However, the absence of known exploits in the wild suggests limited active exploitation currently. Nonetheless, the impact could increase if attackers develop automated or targeted clickjacking campaigns against European entities using vulnerable versions.

CWE-1021Improper Restriction of Rendered UI Layers or Frames (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
Implementation
The use of X-Frame-Options allows developers of web content to restrict the usage of their application within the form of overlays, frames, or iFrames. The developer can indicate from which domains can frame the content.
Implementation
A developer can use a "frame-breaker" script in each page that should not be framed. This is very helpful for legacy browsers that do not support X-Frame-Options security feature previously mentioned.
Implementation
This defense-in-depth technique can be used to prevent the improper usage of frames in web applications. It prioritizes the valid sources of data to be loaded into the application through the usage of declarative policies.
OWASP Cheat Sheets
Content Security Policy (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V14.4.3 (opens in a new tab)
V14.4.7 (opens in a new tab)
Attack patterns
Clickjacking (opens in a new tab)
Flash File Overlay (opens in a new tab)
iFrame Overlay (opens in a new tab)
Task Impersonation (opens in a new tab)
Tapjacking (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Jul 2025, 01:37 UTC

WeaknessesCWE-1021

Technical details

References

Community reviews

Related threats