How severe is GHSA-98pf-gfh3-x3mp?

No CVSS score has been assigned to GHSA-98pf-gfh3-x3mp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-98pf-gfh3-x3mp?

GHSA-98pf-gfh3-x3mp affects the following packages: readthedocs (npm). Ecosystems affected: npm.

How do I fix GHSA-98pf-gfh3-x3mp?

Update readthedocs to 8.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-98pf-gfh3-x3mp is resolved across your whole dependency graph.

How do I detect GHSA-98pf-gfh3-x3mp in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for readthedocs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-98pf-gfh3-x3mp if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-98pf-gfh3-x3mp?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-98pf-gfh3-x3mp can be triaged on real exposure rather than presence alone.

Is GHSA-98pf-gfh3-x3mp actively exploited in the wild?

No public exploit code has been indexed for GHSA-98pf-gfh3-x3mp yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-98pf-gfh3-x3mp published, and has it been updated?

GHSA-98pf-gfh3-x3mp was published on November 10, 2022. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-98pf-gfh3-x3mp — readthedocs

Fix: readthedocs/readthedocs.org@b0ae626

GHSA-98pf-gfh3-x3mp is a security vulnerability in readthedocs. A fix is available for readthedocs — see the affected versions and patch details below.

Read the Docs vulnerable to Cross-Site Scripting (XSS)

Published

Nov 10, 2022

Updated

Nov 10, 2022

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 10, 2022 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦readthedocs

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

This vulnerability allowed a malicious user to serve arbitrary HTML files from the main application domain (readthedocs[.]org/readthedocs[.]com) by exploiting a vulnerability in the code that serves downloadable content from a project.

Exploiting this would have required the attacker to get a logged-in user to visit the malicious URL, which would have allowed the attacker to take control of the user's session with JavaScript (making requests to the API/site on behalf of the user). This URL would have looked something like hxxps[:]//readthedocs[.]org/projects/attacker-project/downloads/html/version-with-javascript-attack/.

Patches

This issue has been patched in our 8.8.1 release.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`readthedocs`	all versions	8.8.1`npm install readthedocs@8.8.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for readthedocs, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update readthedocs to 8.8.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-98pf-gfh3-x3mp is resolved across your whole dependency graph.
Workarounds
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-98pf-gfh3-x3mp can be triaged on real exposure rather than presence alone.

Tailored to GHSA-98pf-gfh3-x3mp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact This vulnerability allowed a malicious user to serve arbitrary HTML files from the main application domain (readthedocs[.]org/readthedocs[.]com) by exploiting a vulnerability in the code that serves downloadable content from a project. Exploiting this would have required the attacker to get a logged-in user to visit the malicious URL, which would have allowed the attacker to take control of the user's session with JavaScript (making requests to the API/site on behalf of the user). This URL would have looked something like `hxxps[:]//readthedocs[.]org/projects/attacker-project/dow

O3 Security · Impact-Aware SCA

Is GHSA-98pf-gfh3-x3mp in your dependencies?

O3 Security finds GHSA-98pf-gfh3-x3mp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works