dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2024-12881

HIGH · 8.8 CVSS v3.1 Published 2024-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
The PlugVersions – Easily rollback to previous versions of your plugins plugin for WordPress is vulnerable to arbitrary file uploads due to a missing capability check on the eos_plugin_reviews_restore_version() function in all versions up to, and including, 0.0.7. This makes it possible for authenticated attackers, with Subscriber-level access and above, to create arbitrary files leveraging files included locally.

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 PlugVersions WordPress plugin contains a broken access control vulnerability in the eos_plugin_reviews_restore_version() function. This function lacks proper capability verification, allowing any authenticated user with Subscriber-level access or higher to trigger arbitrary file creation by leveraging files included locally in the plugin.

MitigationUpdate the PlugVersions plugin to a version beyond 0.0.7 that includes proper capability checks, or if no update is available, disable the plugin until a patched version is released.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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. Confirm PlugVersions plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'PlugVersions' in the list. Note whether it is activated or not.
    Affected if The plugin is installed and activated - the vulnerability only applies to active installations.
  2. Determine installed plugin version
    Click on the PlugVersions plugin in the Plugins list to view its details, or open the main plugin file (usually plugversions.php) and look for the version comment/header.
    Affected if Version is 0.0.7 or lower - the vulnerability exists in these versions. Versions above 0.0.7 contain the fix.
  3. Check for the vulnerable function in plugin code
    Locate the plugin files via FTP or file manager, then search for 'eos_plugin_reviews_restore_version' in the plugin directory files.
    Affected if The function exists in the code - this confirms the vulnerable function is present.
  4. Verify WordPress user roles exist
    In WordPress admin, go to Users > All Users and review the user list. Note if any users with Subscriber, Contributor, Author, Editor, or Administrator roles exist.
    Affected if Any authenticated user with Subscriber-level access or higher exists - this is the condition that makes exploitation possible.
  5. Check capability configuration
    Inspect the plugin code for current_user_capability checks or add_action/add_filter calls related to capability verification around the restore_version function.
    Affected if No capability check (like 'manage_options' or 'edit_plugins') is enforced before the eos_plugin_reviews_restore_version function executes - the vulnerability is present.

If PlugVersions is active, version 0.0.7 or lower, and any subscriber-level or higher user accounts exist in WordPress, the environment is affected by this CVE.

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 PlugVersions plugin to a version beyond 0.0.7 that includes proper capability checks, or if no update is available, disable the plugin until a patched version is released.

Recommended fix High confidence

Version 0.0.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the PlugVersions plugin
  4. Check the current version - if it is 0.0.7 or earlier, it is vulnerable
  5. Click 'Update Now' on the plugin to update to the latest version
  6. Verify the update was successful and the plugin is now running version 0.0.8 or later
  7. If automatic updates are not enabled, manually download the latest version from wordpress.org and upload it via Plugins > Add New > Upload Plugin

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12881 — 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-12881 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