dbcve.org
OptiontreeWordPress extension · Optiontree Project

CVE-2019-15321

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 serialized classes are 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 · high confidence

The option-tree WordPress plugin before version 2.7.3 is vulnerable to PHP Object Injection due to improper handling of serialized data. The plugin mishandles serialized classes during data processing, potentially allowing authenticated attackers to inject malicious PHP objects and achieve remote code execution if suitable POP (property-oriented programming) gadgets exist in the application.

MitigationUpdate the option-tree plugin to version 2.7.3 or later. If immediate update is not possible, disable or remove 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. Locate the option-tree plugin files
    Check the wp-content/plugins directory for a folder named 'option-tree' or inspect the WordPress plugin list via admin panel at Plugins > Installed Plugins
    Affected if The option-tree plugin folder exists in the WordPress installation
  2. Find the installed version number
    Open the main plugin file (typically option-tree/option-tree.php) and locate the version header in the plugin comment block, or check the version specified in the plugin's main PHP file
    Affected if The version field shows a number lower than 2.7.3 (such as 2.7.2, 2.7.1, 2.6.x, etc.)
  3. Verify the plugin is active
    Check the WordPress admin under Plugins > Installed Plugins to confirm option-tree shows as 'Active', or query the wp_options table for the option_name 'option_tree' to see if settings data exists
    Affected if The plugin is currently active and processing data; inactive plugins cannot be exploited
  4. Identify the vulnerable data handling code
    Search plugin PHP files for unserialize() calls, particularly those handling option-tree settings data passed through AJAX actions or theme imports (look for functions processing 'option_tree' or 'ot_settings' POST parameters)
    Affected if Code contains unserialize() calls without prior validation handling plugin settings data

You are affected if the option-tree plugin is installed, active, and its version is below 2.7.3, with vulnerable unserialize() calls present in the code handling serialized data.

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 update is not possible, disable or remove the plugin until the patch can be applied.

Recommended fix High confidence

2.7.3

  1. Backup your WordPress site before making any changes
  2. Navigate to WordPress admin dashboard > Plugins section
  3. Locate the OptionTree plugin in the installed plugins list
  4. Click 'Update now' on the OptionTree plugin to update to version 2.7.3 or later
  5. Verify the plugin version after update shows 2.7.3 or higher
  6. Test that the site functionality remains working as expected after the update

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

Fix this in Optiontree Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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