# GHSA-6qqj-rx4w-r3cj: CSRF Vulnerability in jquery-ujs

> Attackers can leak CSRF tokens to external domains via crafted links, enabling CSRF attacks against users of the jquery-ujs library.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 31 Aug 2020

## What is GHSA-6qqj-rx4w-r3cj?

GHSA-6qqj-rx4w-r3cj is a vulnerability in jquery-ujs, published on 31 Aug 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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 jquery-ujs to version 1.0.4 or later.

## Which versions are affected by GHSA-6qqj-rx4w-r3cj?

2 open source packages ship an affected version, including jquery-ujs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jquery-ujs` | npm | All versions | 1.0.4 |
| `jquery-ujs` | npm | All versions | 1.0.4 |

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

Upgrade jquery-ujs to 1.0.4 or later.

## Is GHSA-6qqj-rx4w-r3cj being exploited?

There is no known exploitation of GHSA-6qqj-rx4w-r3cj in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-6qqj-rx4w-r3cj and fix it if it is affected.

What it is: GHSA-6qqj-rx4w-r3cj is a vulnerability in jquery-ujs, published on 31 Aug 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-6qqj-rx4w-r3cj in the wild and no public exploit code.

Affected packages and fixed versions:
- jquery-ujs (npm): affected all versions; fixed in 1.0.4
- jquery-ujs (npm): affected all versions; fixed in 1.0.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-6qqj-rx4w-r3cj/ (Markdown: https://insights.sbomify.com/GHSA-6qqj-rx4w-r3cj/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-6qqj-rx4w-r3cj

---
From sbomify Insights: https://insights.sbomify.com/GHSA-6qqj-rx4w-r3cj/
Summaries are generated and may contain mistakes; the official description above is the record.