CVE-2025-54129VulnerabilityPublished 21 Jul 2025

CVE-2025-54129: haxtheweb issues · Observable Response Discrepancy

Affects haxtheweb issuesSource CVE Database V5

Not known to be exploited · CVSS 4.3 Medium : upgrade to 11.0.5 when convenient.

Data as of 26 Oct 2026, 06:26 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 25% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 11.0.5

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
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: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within 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 21 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 2026-10-26.

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 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/issues to 11.0.5.

Affected software

Product	Affected	Fixed in
GitHubhaxtheweb/issues`pkg:github/haxtheweb/issues`Other threats	Affected <11.0.5	Fixed in 11.0.5

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

AI-suggested

Organizations should promptly upgrade affected haxtheweb 'issues' products to version 11.0.5 or later, where the vulnerability is fixed. Beyond patching, administrators should implement strict authorization checks to ensure users can only access their own data and microsites, reducing the risk of lateral attacks even if user enumeration occurs. Rate limiting and monitoring of user data requests can help detect and prevent automated brute force username enumeration attempts. Employing multi-factor authentication (MFA) for all authenticated users will further reduce the risk of account compromise. Additionally, security teams should audit existing user permissions and microsite content for unauthorized changes and implement logging and alerting for suspicious activities related to user data access. Finally, educating users about phishing and social engineering risks can mitigate follow-on attacks leveraging enumerated usernames.

Description

HAXiam is a packaging wrapper for HAXcms which allows anyone to spawn their own microsite management platform. In versions 11.0.4 and below, the application returns a 200 response when requesting the data of a valid user and a 404 response when requesting the data of an invalid user. This can be used to infer the existence of valid user accounts. An authenticated attacker can use automated tooling to brute force potential usernames and use the application's response to identify valid accounts. This can be used in conjunction with other vulnerabilities, such as the lack of authorization checks, to enumerate and deface another user's sites. This is fixed in version 11.0.5.

Impact

For European organizations using haxtheweb's HAXiam or HAXcms platforms, this vulnerability poses a risk primarily in the context of information disclosure and subsequent targeted attacks. User enumeration can enable attackers to identify valid accounts, which may be used to launch further attacks such as credential stuffing, phishing, or exploiting authorization weaknesses to deface or manipulate microsites. Given that microsites may be used for marketing, communications, or internal collaboration, unauthorized defacement or data exposure could damage organizational reputation and trust. The impact is heightened for organizations relying heavily on these platforms for public-facing content or internal microsite management. However, since exploitation requires authentication, the risk is somewhat mitigated by existing access controls. The vulnerability does not directly affect system availability or integrity but can be a stepping stone in multi-stage attacks.

Summary

CVE-2025-54129 is a medium-severity vulnerability affecting versions 11.0.4 and below of the 'issues' product within the haxtheweb ecosystem, specifically related to the HAXiam packaging wrapper for HAXcms. The vulnerability arises from an observable response discrepancy when querying user data endpoints. When a request is made for a valid user’s data, the application returns an HTTP 200 status code, whereas a request for an invalid user returns an HTTP 404 status code. This behavior allows an authenticated attacker to enumerate valid usernames by automating requests and analyzing the differing server responses. Although the vulnerability itself does not directly compromise confidentiality, integrity, or availability, it facilitates user enumeration, which can be leveraged in combination with other vulnerabilities such as missing authorization checks to perform more damaging attacks, including unauthorized defacement of user-managed microsites. The flaw is addressed in version 11.0.5 of the software. The CVSS 3.1 base score is 4.3, reflecting a medium severity level, with the vector indicating network attack vector, low attack complexity, requiring privileges, no user interaction, and limited confidentiality impact without integrity or availability impact. No known exploits are currently reported in the wild.

CWE-204Observable Response Discrepancy (opens in a new tab)
Base weakness
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation
Ensure that error messages only contain minimal details that are useful to the intended audience and no one else. The messages need to strike the balance between being too cryptic (which can confuse users) or being too detailed (which may reveal more than intended).
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
ICMP IP Total Length Field Probe (opens in a new tab)
ICMP IP 'ID' Field Error Message Probe (opens in a new tab)
Application Fingerprinting (opens in a new tab)
System Footprinting (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/haxtheweb/issues/security/advisories/GHSA-wh3h-vfcv-m5g5 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Jul 2025, 01:17 UTC

WeaknessesCWE-204

Technical details

References

Community reviews

Related threats