dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2024-54214

CRITICAL · 10.0 CVSS v3.1 Published 2024-12-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unrestricted Upload of File with Dangerous Type vulnerability in roninwp Revy revy allows Upload a Web Shell to a Web Server.This issue affects Revy: from n/a through <= 1.18.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Revy plugin for WordPress contains an unrestricted file upload vulnerability (CWE-434) allowing attackers to upload dangerous file types including web shells. This critical flaw (CVSS 10) enables remote code execution by uploading executable files to the web server.

MitigationUpdate the Revy plugin to a version beyond 1.18 as soon as a patched version is released. Until then, consider disabling the plugin or restricting file upload functionality at the web server level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WordPress installation
    Check for the presence of wp-load.php or wp-config.php in the web root directory
    Affected if WordPress is not installed - this CVE only affects the Revy plugin for WordPress
  2. Identify Revy plugin presence
    Navigate to wp-content/plugins/ directory and check for a folder named 'revy' or 'revy-plugin'. Alternatively, check via WordPress admin under Plugins > Installed Plugins
    Affected if The Revy plugin is not installed - this CVE only applies when the plugin is present
  3. Determine installed Revy plugin version
    Check the main plugin file (usually revy.php or index.php inside the plugin folder) for the 'Version' header in the plugin comments. Alternatively, view the plugin via WordPress admin Plugins page
    Affected if Version is 1.18 or lower, or the version cannot be determined (plugin may be outdated/unmaintained)
  4. Inspect uploaded files directory
    Check the wp-content/uploads/ directory (and any custom upload directories configured in plugin settings) for suspicious file types such as .php, .phtml, .php5, .php7, .phar, .js, .exe, .asp, .aspx that were uploaded recently
    Affected if Unexpected executable or script files are present in upload directories, especially if they were not intentionally uploaded by an administrator
  5. Review server access logs
    Examine web server access logs (Apache access.log, Nginx access.log) for POST requests to /wp-content/uploads/ or the Revy upload endpoint that result in 200 OK responses for file uploads
    Affected if Evidence of file upload requests to the Revy plugin endpoint from unauthorized or unexpected IP addresses

A user is affected if they have the Revy plugin for WordPress installed with version 1.18 or lower, and the plugin's file upload functionality is enabled and publicly accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Revy plugin to a version beyond 1.18 as soon as a patched version is released. Until then, consider disabling the plugin or restricting file upload functionality at the web server level.

Recommended fix Moderate confidence

Latest version of roninwp Revy (version higher than 1.18)

  1. 1. Verify the currently installed version of the roninwp Revy plugin in your WordPress installation
  2. 2. If the installed version is 1.18 or lower, this vulnerability is present
  3. 3. Update the Revy plugin to the latest available version from the WordPress plugin repository or the vendor
  4. 4. After updating, verify the new version number confirms the update was successful
  5. 5. Review the wp-content/uploads directory for any suspicious PHP files that may have been uploaded as web shells
  6. 6. Remove any identified malicious files and investigate for potential compromise
  7. 7. Consider implementing additional file upload validation at the web server level as a defense-in-depth measure

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54214 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-54214 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data