How severe is GHSA-6qqj-rx4w-r3cj?

GHSA-6qqj-rx4w-r3cj has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6qqj-rx4w-r3cj?

GHSA-6qqj-rx4w-r3cj affects the following packages: jquery-ujs (npm). Ecosystems affected: npm.

How do I fix GHSA-6qqj-rx4w-r3cj?

Update jquery-ujs to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qqj-rx4w-r3cj is resolved across your whole dependency graph.

How do I detect GHSA-6qqj-rx4w-r3cj in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jquery-ujs. 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-6qqj-rx4w-r3cj 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-6qqj-rx4w-r3cj?

O3 pinpoints whether GHSA-6qqj-rx4w-r3cj 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-6qqj-rx4w-r3cj actively exploited in the wild?

No public exploit code has been indexed for GHSA-6qqj-rx4w-r3cj 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-6qqj-rx4w-r3cj published, and has it been updated?

GHSA-6qqj-rx4w-r3cj was published on August 31, 2020 and was last updated on September 23, 2021. 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

GHSA-6qqj-rx4w-r3cj

MEDIUM

GHSA-6qqj-rx4w-r3cj is a medium-severity (CVSS 6.5) vulnerability in jquery-ujs. O3 Security confirms whether GHSA-6qqj-rx4w-r3cj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

CSRF Vulnerability in jquery-ujs

Published

Aug 31, 2020

Updated

Sep 23, 2021

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 23, 2021 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

📦jquery-ujs

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

When an attacker controls the href attribute of an anchor tag, or the action attribute of a form tag triggering a POST action, the attacker can set the href or action to " https://attacker.com". By prepending a space to the external domain, it causes jQuery to consider it a same origin request, resulting in the user's CSRF token being sent to the external domain.

Recommendation

Upgrade jquery-ujs to version 1.0.4 or later.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`jquery-ujs`	all versions	1.0.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jquery-ujs. 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 jquery-ujs to 1.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6qqj-rx4w-r3cj 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-6qqj-rx4w-r3cj 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-6qqj-rx4w-r3cj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Versions 1.0.3 and earlier of jquery-ujs are vulnerable to an information leakage attack that may enable attackers to launch CSRF attacks, as it allows attackers to send CSRF tokens to external domains. When an attacker controls the href attribute of an anchor tag, or the action attribute of a form tag triggering a POST action, the attacker can set the href or action to " https://attacker.com". By prepending a space to the external domain, it causes jQuery to consider it a same origin request, resulting in the user's CSRF token being sent to the external domain. ## Recommendation Upgrade j

O3 Security · Impact-Aware SCA

Is GHSA-6qqj-rx4w-r3cj in your dependencies?

O3 detects GHSA-6qqj-rx4w-r3cj across npm 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