# CVE-2020-9322: Cross-site scripting in n/a

> Stored and reflected XSS in Statamic Core allows attackers to add administrator users via CSRF, leading to privilege escalation and account takeover.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-v2qm-4x3j-gc57

## What is CVE-2020-9322?

CVE-2020-9322 is a high-severity cross-site scripting vulnerability in n/a, published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The /users endpoint in Statamic Core before 2.11.8 allows XSS to add an administrator user. This can be exploited via CSRF. Stored XSS can occur via a JavaScript payload in a username during account registration. Reflected XSS can occur via the /users PATH_INFO.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2020-9322?


## How do I fix CVE-2020-9322?

No fix has been published for CVE-2020-9322 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-9322 being exploited?

There is no known exploitation of CVE-2020-9322 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-9322 and fix it if it is affected.

What it is: CVE-2020-9322 is a high-severity cross-site scripting vulnerability in n/a, published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-9322 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2020-9322/ (Markdown: https://insights.sbomify.com/CVE-2020-9322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-9322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-9322
- OSV: https://osv.dev/vulnerability/CVE-2020-9322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-9322/
Summaries are generated and may contain mistakes; the official description above is the record.