dbcve.org
OptiontreeWordPress extension · Optiontree Project

CVE-2019-15320

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 2.7.3 or later.
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 option-tree plugin before 2.7.3 for WordPress has Object Injection because the + character is mishandled.

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 · moderate confidence

The option-tree WordPress plugin before version 2.7.3 is vulnerable to Object Injection due to improper handling of the + character in user input. This allows attackers to potentially inject malicious serialized PHP objects into the application, which could lead to remote code execution if the application unserializes user-controlled data without proper validation.

MitigationUpdate the option-tree plugin to version 2.7.3 or later. If immediate updating is not possible, consider disabling the plugin until the patch can be applied.

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
OptiontreeWordPress extension
Affected:< 2.7.3

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.0/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. Confirm option-tree plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ for the option-tree folder, or log into the WordPress admin dashboard and navigate to Plugins > Installed Plugins to locate option-tree.
    Affected if The option-tree plugin folder exists in the WordPress installation.
  2. Identify the installed version number
    In the WordPress admin, find option-tree in the plugins list and note the version number displayed. Alternatively, open the main plugin file (typically wp-content/plugins/option-tree/option-tree.php) and locate the version comment or Version: header at the top.
    Affected if The displayed version is below 2.7.3.
  3. Verify the vulnerability condition exists
    Since the flaw stems from improper handling of the + character in user input for serialized data, confirm the plugin is active and its settings import functionality (which processes serialized option data) is accessible. Check if the plugin processes user-supplied option data through the ot_validate_setting() function or similar input handlers.
    Affected if The plugin version is below 2.7.3 AND the plugin is active with input handling functionality present.

A user is affected if the option-tree plugin version is below 2.7.3 and the plugin is installed and active in their WordPress environment.

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 2.7.3 or later
Fixed in 2.7.3
Interim mitigation

Update the option-tree plugin to version 2.7.3 or later. If immediate updating is not possible, consider disabling the plugin until the patch can be applied.

Recommended fix High confidence

2.7.3

  1. Backup your WordPress site and database before making any changes
  2. Navigate to the WordPress admin dashboard
  3. Go to Plugins > Installed Plugins
  4. Find the Option Tree plugin
  5. Click 'Update now' to install version 2.7.3 or later, or manually upload the latest version from wordpress.org if automatic update is not available
  6. Verify the plugin version shows 2.7.3 or higher after updating
  7. Test critical site functionality to ensure the plugin continues to work correctly

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

Fix this in Optiontree 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 the upgrade done

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-2019-15320 — 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-2019-15320 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