Administrator self-XSS via unescaped broken theme name
Published Jun 12, 2020 · Updated Aug 4, 2024
Cross-site scripting in affected WordPress releases allows administrators to execute JavaScript via a crafted theme folder name. The broken-theme row in wp-admin/themes.php prints get_stylesheet() directly when a theme lacks a Name value, without HTML-escaping the folder-derived string. Exploitation requires an administrator to upload the crafted theme and open the Themes page, so script execution is confined to that administrator's browser session.
Summary
What happened
Cross-site scripting in affected WordPress releases allows administrators to execute JavaScript via a crafted theme folder name. The broken-theme row in wp-admin/themes.php prints get_stylesheet() directly when a theme lacks a Name value, without HTML-escaping the folder-derived string. Exploitation requires an administrator to upload the crafted theme and open the Themes page, so script execution is confined to that administrator's browser session.
The record
- CVE
- CVE-2020-4049
- Published
- Jun 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- WordPress.org
- Product
- WordPress
- Classifications
- CWE-79, CWE-80, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 12, 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.34
- Affected versionversion=>= 3.8.0, < 3.8.34
- Affected versionversion=>= 3.9.0, < 3.9.32
- Affected versionversion=>= 4.0.0, < 4.0.31
- Affected versionversion=>= 4.1.0, < 4.1.31
- Affected versionversion=>= 4.2.0, < 4.2.28
- Affected versionversion=>= 4.3.0, < 4.3.24
- Affected versionversion=>= 4.4.0, < 4.4.23
- Affected versionversion=>= 4.5.0, < 4.5.22
- Affected versionversion=>= 4.6.0, < 4.6.19
- Affected versionversion=>= 4.7.0, < 4.7.18
- Affected versionversion=>= 4.8.0, < 4.8.14
- Affected versionversion=>= 4.9.0, < 4.9.15
- Affected versionversion=>= 5.0.0, < 5.0.10
- Affected versionversion=>= 5.1.0, < 5.1.6
- Affected versionversion=>= 5.2.0, < 5.2.7
- Affected versionversion=>= 5.3.0, < 5.3.4
- Affected versionversion=>= 5.4.0, < 5.4.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.
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