dbcve.org
Option EditorApplication · Backie

CVE-2024-13852

HIGH · 8.8 CVSS v3.1 Published 2025-02-18
Fix available
A fix is available. Upgrade to after 1.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Option Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in version 1.0. This is due to missing nonce validation on the plugin_page() function. This makes it possible for unauthenticated attackers to update arbitrary options on the WordPress site via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link. This can be leveraged to update the default role for registration to administrator and enable user registration for attackers to gain administrative user access to a vulnerable site.

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 Option Editor WordPress plugin v1.0 is vulnerable to CSRF due to missing nonce validation on the plugin_page() function. Attackers can forge requests to update arbitrary WordPress options, specifically enabling user registration and setting the default role to administrator, then registering an admin account to gain full site control.

MitigationAdd nonce validation to the plugin_page() function and all state-changing operations; update to a patched version if available, otherwise remove the plugin.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Option EditorApplication
Affected:<= 1.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Check if Backie Option Editor plugin is installed
    Inspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'backie-option-editor' or similar. Alternatively, log into WordPress admin and navigate to Plugins > Installed Plugins and search for 'Option Editor' or 'Backie'.
    Affected if The plugin folder exists in wp-content/plugins/ or the plugin appears in the WordPress admin plugins list.
  2. Verify the installed plugin version
    If the plugin is found, open its main PHP file (usually in the plugin root folder) and locate the plugin header comment containing 'Version: x.x'. Compare this version number to the affected range: <= 1.0.
    Affected if The plugin version is 1.0 or lower.
  3. Confirm the plugin is active
    Check if the plugin is currently activated. In WordPress admin > Plugins > Installed Plugins, verify the plugin does not have a 'Deactivated' status. Alternatively, query the wp_options table for the 'active_plugins' option and check if the plugin's main file is listed.
    Affected if The plugin appears as 'Active' in WordPress admin or its entry is present in the active_plugins option array.
  4. Identify the vulnerable function location
    Locate the plugin_page() function within the plugin files. Check the plugin's main PHP file or any admin-related PHP files for a function named 'plugin_page' that handles option updates without nonce verification.
    Affected if The plugin_page() function exists in the plugin code and lacks nonce validation logic (no wp_verify_nonce, check_admin_referer, or similar calls).

You are affected if the Backie Option Editor plugin is installed at version 1.0 or lower, is currently active, and contains the plugin_page() function without CSRF protection measures.

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
Upgrade available Upgrade to a release after 1.0
Interim mitigation

Add nonce validation to the plugin_page() function and all state-changing operations; update to a patched version if available, otherwise remove the plugin.

Recommended fix Moderate confidence

latest available version on wordpress.org (check for version > 1.0)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the Option Editor plugin
  4. 4. Check if an update is available for the Option Editor plugin
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. Alternatively, manually download the latest version from wordpress.org/plugins/option-editor/ and upload via Plugins > Add New > Upload Plugin
  7. 7. After updating, verify the plugin is functioning correctly

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

Fix this in Option Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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