# CVE-2021-25026: Patreon WordPress < 1.8.2 - Admin+ Stored Cross-Site Scripting

> High-privilege users can inject malicious scripts via the Custom Patreon Page name field, potentially compromising admin sessions.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Mar 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-84ph-h2vc-8hrg

## What is CVE-2021-25026?

CVE-2021-25026 is a medium-severity cross-site scripting vulnerability in Unknown Patreon WordPress, published on 14 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Patreon WordPress plugin before 1.8.2 does not sanitise and escape the field "Custom Patreon Page name", which could allow high privilege users to perform Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2021-25026?

It affects 1 product.


Products: Patreon Patreon Wordpress.

## How do I fix CVE-2021-25026?

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

## Is CVE-2021-25026 being exploited?

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

## Other vulnerabilities in Unknown Patreon WordPress

- [CVE-2018-20984](https://insights.sbomify.com/CVE-2018-20984/): Deserialization in n/a (critical 9.8)
- [CVE-2021-24228](https://insights.sbomify.com/CVE-2021-24228/): Patreon WordPress < 1.7.2 - Reflected XSS on Login Form (critical 9.6)
- [CVE-2021-24229](https://insights.sbomify.com/CVE-2021-24229/): Patreon WordPress < 1.7.2 - Reflected XSS on patreon_save_attachment_patreon_level AJAX action (critical 9.6)
- [CVE-2021-24230](https://insights.sbomify.com/CVE-2021-24230/): Patreon WordPress < 1.7.0 - CSRF to Overwrite/Create User Meta (high 8.1)
- [CVE-2021-24227](https://insights.sbomify.com/CVE-2021-24227/): Patreon WordPress < 1.7.0 - Unauthenticated Local File Disclosure (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-25026 and fix it if it is affected.

What it is: CVE-2021-25026 is a medium-severity cross-site scripting vulnerability in Unknown Patreon WordPress, published on 14 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-25026 in the wild and no public exploit code.

Affected product: Unknown Patreon WordPress. 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-2021-25026/ (Markdown: https://insights.sbomify.com/CVE-2021-25026/index.md)
```

## Sources

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

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