GHSA-2wqw-hr4f-xrhh is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in rsshub. O3 Security confirms whether GHSA-2wqw-hr4f-xrhh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
RSSHub Cross-site Scripting vulnerability caused by internal media proxy
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
rsshubnpmDescription
Impact
When the specially crafted image is supplied to the internal media proxy, it proxies the image without handling XSS vulnerabilities, allowing for the execution of arbitrary JavaScript code.
Users who access the deliberately constructed URL are affected.
Patches
This vulnerability was fixed in version https://github.com/DIYgod/RSSHub/commit/4d3e5d79c1c17837e931b4cd253d2013b487aa87. Please upgrade to this or a later version.
Workarounds
No.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | rsshub | ≥ 1.0.0-master.cbbd829&&< 1.0.0-master.d8ca915 | 1.0.0-master.d8ca915 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rsshub. 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 rsshub to 1.0.0-master.d8ca915 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2wqw-hr4f-xrhh 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-2wqw-hr4f-xrhh 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-2wqw-hr4f-xrhh. 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-2wqw-hr4f-xrhh in your dependencies?
O3 detects GHSA-2wqw-hr4f-xrhh across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.