Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-31210PHP file upload bypass via Plugin installer

Description

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

  1. ID reserved

    By GitHub_M

  2. · 6 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-31210, by who scored it
Scored byCVSSScoreVector
GitHub_MCNA (assigner)3.1High7.7CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H
NVDNVD · Analyzed3.1High8.8CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
1.00% · top 37% of all CVEs (18 Nov 2026)
CISA SSVC
Exploitation: none · Automatable: no · Technical impact: total
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.7.

Affected products

  • WordPress · wordpress-develop

    • affected >= 6.4.0, < 6.4.3
    • affected >= 6.3.0, < 6.3.3
    • affected >= 6.2.0, < 6.2.4
    • affected >= 6.1.0, < 6.1.5
    • affected >= 6.0.0, < 6.0.7
    • affected >= 5.9.0, < 5.9.9
    • affected >= 5.8.0, < 5.8.9
    • affected >= 5.7.0, < 5.7.11
    • affected >= 5.6.0, < 5.6.13
    • affected >= 5.5.0, < 5.5.14
    • affected >= 5.4.0, < 5.4.15
    • affected >= 5.3.0, < 5.3.17
    • affected >= 5.2.0, < 5.2.20
    • affected >= 5.1.0, < 5.1.18
    • affected >= 5.0.0, < 5.0.21
    • affected >= 4.9.0, < 4.9.25
    • affected >= 4.8.0, < 4.8.24
    • affected >= 4.7.0, < 4.7.28
    • affected >= 4.6.0, < 4.6.28
    • affected >= 4.5.0, < 4.5.31
    • affected >= 4.4.0, < 4.4.32
    • affected >= 4.3.0, < 4.3.33
    • affected >= 4.2.0, < 4.2.37
    • affected < 4.1.40

References

References1

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-31210 badge
[![CVE-2024-31210](https://cveledger.app/badge/CVE-2024-31210.svg)](https://cveledger.app/cve/CVE-2024-31210)

Record last updated .