PHP file upload bypass via Plugin installer
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.4.3, 6.3.3, 6.2.4, 6.1.5, 6.0.7, and 19 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
WordPress is an open publishing platform for the Web. It's possible for a file of a type other than a zip file to be submitted as a new plugin by an administrative user on the Plugins -> Add New -> Upload Plugin screen in WordPress. If FTP credentials are requested for installation (in order to move the file into place outside of the `uploads` directory) then the uploaded file remains temporary available in the Media Library despite it not being allowed. If the `DISALLOW_FILE_EDIT` constant is set to `true` on the site and FTP credentials are required when uploading a new theme or plugin, then this technically allows an RCE when the user would otherwise have no means of executing arbitrary PHP code. This issue only affects Administrator level users on single site installations, and Super Admin level users on Multisite installations where it's otherwise expected that the user does not have permission to upload or execute arbitrary PHP code. Lower level users are not affected. Sites where the `DISALLOW_FILE_MODS` constant is set to `true` are not affected. Sites where an administrative user either does not need to enter FTP credentials or they have access to the valid FTP credentials, are not affected. The issue was fixed in WordPress 6.4.3 on January 30, 2024 and backported to versions 6.3.3, 6.2.4, 6.1.5, 6.0.7, 5.9.9, 5.8.9, 5.7.11, 5.6.13, 5.5.14, 5.4.15, 5.3.17, 5.2.20, 5.1.18, 5.0.21, 4.9.25, 2.8.24, 4.7.28, 4.6.28, 4.5.31, 4.4.32, 4.3.33, 4.2.37, and 4.1.40. A workaround is available. If the `DISALLOW_FILE_MODS` constant is defined as `true` then it will not be possible for any user to upload a plugin and therefore this issue will not be exploitable.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- WordPress wordpress-develop
From 6.4.0 · fixed in 6.4.3; From 6.3.0 · fixed in 6.3.3; From 6.2.0 · fixed in 6.2.4; From 6.1.0 · fixed in 6.1.5; From 6.0.0 · fixed in 6.0.7; From 5.9.0 · fixed in 5.9.9; From 5.8.0 · fixed in 5.8.9; From 5.7.0 · fixed in 5.7.11; From 5.6.0 · fixed in 5.6.13; From 5.5.0 · fixed in 5.5.14; From 5.4.0 · fixed in 5.4.15; From 5.3.0 · fixed in 5.3.17; From 5.2.0 · fixed in 5.2.20; From 5.1.0 · fixed in 5.1.18; From 5.0.0 · fixed in 5.0.21; From 4.9.0 · fixed in 4.9.25; From 4.8.0 · fixed in 4.8.24; From 4.7.0 · fixed in 4.7.28; From 4.6.0 · fixed in 4.6.28; From 4.5.0 · fixed in 4.5.31; From 4.4.0 · fixed in 4.4.32; From 4.3.0 · fixed in 4.3.33; From 4.2.0 · fixed in 4.2.37; fixed in 4.1.40