dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-12209

CRITICAL · 9.8 CVSS v3.1 Published 2024-12-08
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
The WP Umbrella: Update Backup Restore & Monitoring plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.17.0 via the 'filename' parameter of the 'umbrella-restore' action. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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 WP Umbrella plugin for WordPress versions up to 2.17.0 contains an unauthenticated Local File Inclusion vulnerability in the 'umbrella-restore' action via the 'filename' parameter. Attackers can include arbitrary files from the server filesystem, leading to remote code execution when PHP files are included and executed.

MitigationImmediately update the WP Umbrella plugin to a version beyond 2.17.0. Since this is an unauthenticated vulnerability with RCE potential, audit the WordPress installation for signs of compromise, including newly uploaded malicious files or unauthorized admin accounts.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify installed WP Umbrella plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Umbrella. Note the version number shown. Alternatively, check the main plugin file header in /wp-content/plugins/umbrella/ directory.
    Affected if Version is 2.17.0 or lower
  2. Confirm umbrella-restore endpoint is reachable
    Make a GET request to your WordPress site with parameters action=umbrella-restore and filename=test (for example: yoursite.com/?action=umbrella-restore&filename=test). Observe if the endpoint processes the request without requiring authentication.
    Affected if Endpoint responds without authentication check
  3. Check plugin directory for suspicious files
    List all files in /wp-content/plugins/umbrella/ directory. Look for unfamiliar PHP files with random names, recently created files that do not match your plugin update history, or webshell-style filenames.
    Affected if Unexpected PHP files exist that were not part of the original plugin distribution

You are affected if WP Umbrella plugin version 2.17.0 or lower is installed and the umbrella-restore action is accessible without authentication.

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

Immediately update the WP Umbrella plugin to a version beyond 2.17.0. Since this is an unauthenticated vulnerability with RCE potential, audit the WordPress installation for signs of compromise, including newly uploaded malicious files or unauthorized admin accounts.

Recommended fix Moderate confidence

Version 2.17.1 or later (check WordPress plugin repository for latest stable release)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard.
  3. 3. Find the 'WP Umbrella: Update Backup Restore & Monitoring' plugin.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Alternatively, download the updated plugin from the official WordPress plugin repository (plugins.trac.wordpress.org) and upload it manually.
  6. 6. Verify the plugin is updated to version 2.17.1 or later.
  7. 7. Test that the 'umbrella-restore' functionality still works correctly after the update.

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
  • Testing2.0 h
5.0 hours of engineering $880
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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