Stored XSS via incomplete UTF-8 filename sanitization
Published Apr 30, 2020 · Updated Aug 4, 2024
Stored cross-site scripting in WordPress 3.7 through 5.4 allows remote authenticated users to execute script via crafted media filenames. The sanitize_file_name function failed to normalize invalid UTF-8 bytes before accepting a stored filename, allowing browser-interpreted content to survive sanitization. An authenticated account with media-upload privileges must store the file, and script runs only when the uploaded file is accessed in a browser.
Summary
What happened
Stored cross-site scripting in WordPress 3.7 through 5.4 allows remote authenticated users to execute script via crafted media filenames. The sanitize_file_name function failed to normalize invalid UTF-8 bytes before accepting a stored filename, allowing browser-interpreted content to survive sanitization. An authenticated account with media-upload privileges must store the file, and script runs only when the uploaded file is accessed in a browser.
The record
- CVE
- CVE-2020-11026
- Published
- Apr 30, 2020
- Updated
- Aug 4, 2024
- Vendor
- WordPress.org
- Product
- WordPress
- Classifications
- CWE-79, CWE-707, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>= 3.7.0, < 3.7.33
- Affected versionversion=>= 3.8.0, < 3.8.33
- Affected versionversion=>= 3.9.0, < 3.9.31
- Affected versionversion=>= 4.0.0, < 4.0.30
- Affected versionversion=>= 4.1.0, < 4.1.30
- Affected versionversion=>= 4.2.0, < 4.2.27
- Affected versionversion=>= 4.3.0, < 4.3.23
- Affected versionversion=>= 4.4.0, < 4.4.22
- Affected versionversion=>= 4.5.0, < 4.5.21
- Affected versionversion=>= 4.6.0, < 4.6.18
- Affected versionversion=>= 4.7.0, < 4.7.17
- Affected versionversion=>= 4.8.0, < 4.8.13
- Affected versionversion=>= 4.9.0, < 4.9.14
- Affected versionversion=>= 5.0.0, < 5.0.9
- Affected versionversion=>= 5.1.0, < 5.1.5
- Affected versionversion=>= 5.2.0, < 5.2.6
- Affected versionversion=>= 5.3.0, < 5.3.3
- Affected versionversion=>= 5.4.0, < 5.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
Weakness, pattern, technique
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