How severe is GHSA-xgfm-fjx6-62mj?

GHSA-xgfm-fjx6-62mj has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xgfm-fjx6-62mj?

GHSA-xgfm-fjx6-62mj affects the following packages: readthedocs-sphinx-search (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-xgfm-fjx6-62mj?

Update readthedocs-sphinx-search to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xgfm-fjx6-62mj is resolved across your whole dependency graph.

How do I detect GHSA-xgfm-fjx6-62mj in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for readthedocs-sphinx-search. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xgfm-fjx6-62mj 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-xgfm-fjx6-62mj?

O3 pinpoints whether GHSA-xgfm-fjx6-62mj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xgfm-fjx6-62mj actively exploited in the wild?

No public exploit code has been indexed for GHSA-xgfm-fjx6-62mj 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-xgfm-fjx6-62mj published, and has it been updated?

GHSA-xgfm-fjx6-62mj was published on January 16, 2024 and was last updated on November 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-xgfm-fjx6-62mj

MEDIUM

readthedocs-sphinx-search vulnerable to cross-site scripting when including search results from malicious projects

Published

Jan 16, 2024

Updated

Nov 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Blast Radius

1 pkg affected

🐍readthedocs-sphinx-search

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

Description

Impact

This vulnerability could have allowed an attacker to include arbitrary HTML content in search results by having a user search a malicious project. This was due to our search client not correctly escaping all user content from search results. You can find more information in the advisory published in our readthedocs.org repo.

Users of this extension should update to the 0.3.2 version, and trigger a new build.

This issue was discovered by a member of our team, and we have seen no signs that this vulnerability was exploited in the wild.

Patches

This issue has been patched in our 0.3.2 version.

References

https://github.com/readthedocs/readthedocs-sphinx-search/commit/8c6f6d01e88e72ef32ed0c220b6c19d1e1121c73

For more information

If you have any questions or comments about this advisory, email us at [email protected] (PGP)

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`readthedocs-sphinx-search`	all versions	0.3.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for readthedocs-sphinx-search. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update readthedocs-sphinx-search to 0.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xgfm-fjx6-62mj 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 pinpoints whether GHSA-xgfm-fjx6-62mj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xgfm-fjx6-62mj. 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 could have allowed an attacker to include arbitrary HTML content in search results by having a user search a malicious project. This was due to our search client not correctly escaping all user content from search results. You can find more information in the [advisory published in our readthedocs.org repo](https://github.com/readthedocs/readthedocs.org/security/advisories/GHSA-qhqx-5j25-rv48). Users of this extension should update to the 0.3.2 version, and trigger a new build. This issue was discovered by a member of our team, and we have seen no signs that th

O3 Security · Impact-Aware SCA

Is GHSA-xgfm-fjx6-62mj in your dependencies?

O3 detects GHSA-xgfm-fjx6-62mj across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works