GHSA-fvx2-x7ff-fc56 is a medium-severity (CVSS 5.3) CWE-201 vulnerability in @haxtheweb/open-apis. No vendor fix is recorded yet; mitigation options are listed below.
Unauthenticated Disclosure of PSU HAX CMS Site Listings via haxPsuUsage API Endpoint
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-fvx2-x7ff-fc56.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-fvx2-x7ff-fc56 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@haxtheweb/open-apisnpmDescription
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 privacy and enumeration risk.
PoC
To reproduce this vulnerability:
- Open a terminal or browser.
- Send a GET request to the following endpoint:
curl https://open-apis.hax.cloud/api/services/stats/haxPsuUsage
Impact
The haxPsuUsage endpoint exposes a full list of PSU HAX CMS websites to any unauthenticated user, allowing external actors to enumerate all sites under the PSU domain. This alone represents an information disclosure vulnerability.
When chained with the Lack Of Authorization Checks CVE, which involves missing authorization checks on key API endpoints, the risk escalates significantly. An authenticated attacker can:
- Modify or delete other users' sites via:
createNode(),saveNode(),deleteNode()
- Access sensitive metadata or credentials:
getConfig(),downloadSite()
- Clone or remove entire sites:
cloneSite(),deleteSite(),archiveSite()
Combined, these issues allow a low-privileged user to fully compromise any site in the PSU HAX CMS instance.
This vulnerability chain puts content integrity, availability, and confidentiality at risk for potentially hundreds of PSU academic, instructional, and departmental sites.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @haxtheweb/open-apis | all versions | No fix |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @haxtheweb/open-apis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of @haxtheweb/open-apis has shipped for GHSA-fvx2-x7ff-fc56 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-fvx2-x7ff-fc56 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-fvx2-x7ff-fc56. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fvx2-x7ff-fc56 in your dependencies?
O3 Security finds GHSA-fvx2-x7ff-fc56 across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.