CVE-2025-48996: haxtheweb issues · Insertion of Sensitive Information Into Sent Data
Affects haxtheweb issuesSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 3.1 : update haxtheweb issues when convenient.
Data as of 26 Oct 2026, 17:16 UTC
- 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 3.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 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.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubhaxtheweb/open-apispkg:github/haxtheweb/open-apisOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediate patching: European organizations using HAX CMS should upgrade their open-apis component to versions later than 10.0.2 where the vulnerability is fixed (commit 06c2e1fbb7131a8fe66aa0600f38dcacae6b7ac7).
- Access control review: Implement strict access controls and authentication mechanisms on all API endpoints, especially those exposing infrastructure or usage data, to prevent unauthenticated access.
- API endpoint monitoring: Deploy logging and monitoring solutions to detect unusual or unauthorized API requests, enabling early detection of reconnaissance activities.
- Security testing: Conduct regular security assessments and penetration testing focusing on chained vulnerabilities that could escalate the impact of information disclosure flaws.
- Network segmentation: Restrict API endpoint access to trusted networks or VPNs where feasible to reduce exposure to external attackers.
- Incident response readiness: Prepare response plans for potential content tampering incidents that could arise from chained exploitation scenarios.
- Vendor engagement: Maintain communication with the HAX CMS vendor or community for timely updates and security advisories.
Description
HAX open-apis provides microservice apis for HAX webcomponents repo that are shared infrastructure calls. An unauthenticated information disclosure vulnerability exists in the Penn State University deployment of the HAX content management system via the `haxPsuUsage` API endpoint, related to a flat present in open-apis versions up to and including 10.0.2. This allows any remote unauthenticated user to retrieve a full list of PSU websites hosted on HAX CMS. When chained with other authorization issues (e.g., HAX-3), this could assist in targeted attacks such as unauthorized content modification or deletion. Commit 06c2e1fbb7131a8fe66aa0600f38dcacae6b7ac7 patches the vulnerability.