GHSA-v3ph-2q5q-cg88 CVE-2025-49139
@haxtheweb/haxcms-nodejs Iframe Phishing vulnerability
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.37%
- Chance of exploitation in the next 30 days. Higher than 30.89% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-1021 Improper Restriction of Rendered UI Layers or Frames
- Fix
11.0.0- Upgrade @haxtheweb/haxcms-nodejs to this version or later
Description
Summary
In the HAX site editor, users can create a website block to load another site in an iframe. The application allows users to supply a target URL in the website block. When the HAX site is visited, the client's browser will query the supplied URL.
Affected Resources
- Operations.php:868
https://<site>/<user>/system/api/saveNode
PoC
- Set the URL in an iframe pointing to an attacker-controlled server running Responder
- Once another user visits the site, they are prompted to sign in.
- If a user inputs credentials, the username and password hash are outputted in Responder.
Impact
An authenticated attacker can create a HAX site with a website block pointing at an attacker-controlled server running Responder or a similar tool. The attacker can then conduct a phishing attack by convincing another user to visit their malicious HAX site to harvest credentials.
Affected versions
npm
| Package | Vulnerable | Fixed in |
|---|---|---|
| @haxtheweb/haxcms-nodejs | < 11.0.0 |
11.0.0 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
@haxtheweb/haxcms-nodejs npm → 11.0.0
- npm
npm install @haxtheweb/haxcms-nodejs@11.0.0- yarn
yarn add @haxtheweb/haxcms-nodejs@11.0.0- pnpm
pnpm add @haxtheweb/haxcms-nodejs@11.0.0
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:N
- Attack vector
- Network
- Attack complexity
- High
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Weakness
CWE-1021: Improper Restriction of Rendered UI Layers or Frames
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
How to prevent it
- 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. The concept of X-Frame-Options is well documented, but implementation of this protection mechanism is in development to cover gaps. There is a need for allowing frames from multiple domains.
- 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. It is also important to note that this tactic has been circumvented or bypassed. Improper usage of frames can persist in the web application through nested frames. The "frame-breaking" script does not intuitively account for multiple nested frames that can be presented to the user.
- 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. Based on which implementation of Content Security Policy is in use, the developer should use the "frame-ancestors" directive or the "frame-src" directive to mitigate this weakness. Both directives allow for the placement of restrictions when it comes to allowing embedded content.
- Implementation: In addition to frames or iframes as previously mentioned, the web application is expected to place restrictions on whether it is allowed to be rendered within objects, embed, or applet elements.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-g2g8-95qg-v35h HaxCMS has a stored Cross-Site Scripting (XSS) bypass in its saveNode endpoint | High | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-9r33-xhw8-4qqp HAX CMS: Denial of Service using Malicious Import Request | Medium | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-x3x5-7h4h-gwxg HAXcms: Mass Token Exfiltration and Cross-Tenant Hijack | High | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-jh3h-rpxg-fr36 Stored XSS via <iframe> in HAX CMS allows access to sensitive client-side data and account takeover | High | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-6c8g-9hfh-pq5h HAXcms: Private Key Disclosure via Broken HMAC Implementation | Critical | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-2m6p-hm3w-6jm3 HAX CMS: Stored XSS via '<video-player>' component allows arbitrary JavaScript execution and token theft | Medium | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-q862-gcgq-5m6g HAXcms createSite SSRF Enables Arbitrary File Read | High | Also affects @haxtheweb/haxcms-nodejs |
| GHSA-3fm2-xfq7-7778 HAXcms Has Stored XSS Vulnerability that May Lead to Account Takeover | Medium | Also affects @haxtheweb/haxcms-nodejs |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor