Admin stored XSS via unsanitized page name
Published Mar 14, 2022 · Updated Aug 3, 2024
Cross-site scripting in Patreon WordPress before 1.8.2 allows remote authenticated users to inject scripts via the Custom Patreon Page name field. The plugin stores and renders that field without sufficient sanitization or escaping, allowing attacker-supplied markup to execute in a victim's browser. Exploitation requires a high-privilege WordPress account and a victim viewing the affected page; the consequence is script-driven page manipulation or access to data available in that browser context.
Summary
What happened
Cross-site scripting in Patreon WordPress before 1.8.2 allows remote authenticated users to inject scripts via the Custom Patreon Page name field. The plugin stores and renders that field without sufficient sanitization or escaping, allowing attacker-supplied markup to execute in a victim's browser. Exploitation requires a high-privilege WordPress account and a victim viewing the affected page; the consequence is script-driven page manipulation or access to data available in that browser context.
The record
- CVE
- CVE-2021-25026
- Published
- Mar 14, 2022
- Updated
- Aug 3, 2024
- Vendor
- Patreon
- Product
- Patreon WordPress
- Classifications
- CWE-79, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 14, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.8.2 <1.8.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo