How severe is GHSA-2wqw-hr4f-xrhh?

GHSA-2wqw-hr4f-xrhh has a CVSS score of 6.1/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-2wqw-hr4f-xrhh?

GHSA-2wqw-hr4f-xrhh affects the following packages: rsshub (npm). Ecosystems affected: npm.

How do I fix GHSA-2wqw-hr4f-xrhh?

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.

How do I detect GHSA-2wqw-hr4f-xrhh in my npm dependencies?

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

How do I mitigate GHSA-2wqw-hr4f-xrhh if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-2wqw-hr4f-xrhh actively exploited in the wild?

No public exploit code has been indexed for GHSA-2wqw-hr4f-xrhh 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.

What is the EPSS score for GHSA-2wqw-hr4f-xrhh?

GHSA-2wqw-hr4f-xrhh has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 44th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-2wqw-hr4f-xrhh?

GHSA-2wqw-hr4f-xrhh is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-2wqw-hr4f-xrhh published, and has it been updated?

GHSA-2wqw-hr4f-xrhh was published on March 6, 2024 and was last updated on September 10, 2026. 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

MEDIUM severity

RSSHub Cross-site Scripting vulnerability caused by internal media proxyGHSA-2wqw-hr4f-xrhh

MEDIUMFix: DIYgod/RSSHub@4d3e5d7

GHSA-2wqw-hr4f-xrhh is a medium-severity (CVSS 6.1) Cross-site Scripting (XSS) vulnerability in rsshub. A fix is available for rsshub — see the affected versions and patch details below.

Also known asCVE-2024-27926

Published

Mar 6, 2024

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

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-2wqw-hr4f-xrhh.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

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.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

rsshubnpm

24Kdownloads / week

Description

RSSHub is an open source RSS feed generator. Starting in version 1.0.0-master.cbbd829 and prior to version 1.0.0-master.d8ca915, ahen 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. This vulnerability was fixed in version 1.0.0-master.d8ca915. No known workarounds are available.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`rsshub`	≥ 1.0.0-master.cbbd829&&< 1.0.0-master.d8ca915	1.0.0-master.d8ca915`npm install rsshub@1.0.0-master.d8ca915`

Affected Products

1 product · 1 configurations

Application

rsshubrsshub

≥ 1.0.0-master.cbbd829 && < 1.0.0-master.d8ca915

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for rsshub, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

## 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.