Unauthenticated Disclosure of PSU HAX CMS Site Listings via haxPsuUsage API Endpoint
CVE-2025-48996GHSA-fvx2-x7ff-fc56
What to do
Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
npm @haxtheweb/open-apis
- Affected
- <= 10.0.1
- Fixed in
- no fixed version recorded
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-fvx2-x7ff-fc56 lists affected ranges: npm @haxtheweb/open-apis >=0 <=10.0.1
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-fvx2-x7ff-fc56 lists affected ranges: npm @haxtheweb/open-apis >=0 <=10.0.1
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- EPSS
- CVE-2025-48996: 0.37% estimated exploitation activity in the next 30 days; percentile 31.25 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An unauthenticated information disclosure vulnerability exists in the PSU deployment of HAX CMS via the haxPsuUsage API endpoint. 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. --- Details The endpoint https://open-apis.hax.cloud/api/services/stats/haxPsuUsage returns a list of websites on the PSU instance of HAX CMS. This endpoint is exposed without any authentication or authorization checks. The source of the issue is in the haxPsuUsage.js file, which appears to directly serve the site listing without verifying user identity or access level. This enables anyone with the endpoint URL to enumerate all site instances under the PSU deployment. This endpoint may have originally been used for internal or statistical purposes but is now publicly accessible, representing a…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-fvx2-x7ff-fc56
- Revision 1 · created ·
Published from osv record GHSA-fvx2-x7ff-fc56
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-48996 Advisory: Unauthenticated Disclosure of PSU HAX CMS Site Listings via haxPsuUsage API Endpoint IDs: CVE-2025-48996, GHSA-fvx2-x7ff-fc56 Record: https://patchnext.com/advisories/cve-2025-48996 (revision 2, source checked 26 Oct 2026, 12:37 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed. ## Affected components - npm @haxtheweb/open-apis: affected <= 10.0.1 ## Suggested inspection (read-only) - `npm ls @haxtheweb/open-apis --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on @haxtheweb/open-apis. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GHSA-fvx2-x7ff-fc56 (OSV record GHSA-fvx2-x7ff-fc56 lists affected ranges: npm @haxtheweb/open-apis >=0 <=10.0.1) - Verified: https://github.com/advisories/GHSA-fvx2-x7ff-fc56 (GitHub-reviewed advisory GHSA-fvx2-x7ff-fc56 lists affected ranges: npm @haxtheweb/open-apis >=0 <=10.0.1) Commands are suggestions: review each one before running it.
Loading voting…