dbcve.org
OptiontreeWordPress extension · Optiontree Project

CVE-2019-15319

CRITICAL · 9.8 CVSS v3.0 Published 2019-08-22
Fix available
A fix is available. Upgrade to 2.7.0 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.0 for WordPress has Object Injection by leveraging a valid nonce.

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

This is a PHP Object Injection vulnerability in the OptionTree WordPress plugin (versions before 2.7.0) that allows attackers with a valid nonce to deserialize untrusted input, potentially achieving remote code execution if suitable PHP magic methods exist in the application or installed plugins.

MitigationUpdate the OptionTree plugin to version 2.7.0 or later to remediate the object injection vulnerability.

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.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
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. Verify OptionTree plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'OptionTree' in the list, or check for the presence of /wp-content/plugins/option-tree/ directory in the file system
    Affected if OptionTree plugin is not found in the WordPress installation
  2. Check installed OptionTree version
    In WordPress admin, go to Plugins > Installed Plugins > OptionTree, or open the main plugin file (option-tree.php) and look for the 'Version:' header comment, or check /wp-content/plugins/option-tree/readme.txt for the stable tag
    Affected if The version shown is lower than 2.7.0 (for example 2.6.0, 2.5.0, etc.)
  3. Confirm the vulnerable deserialization code exists
    Examine the file /wp-content/plugins/option-tree/includes/ot-functions-admin-settings.php (or similar admin handling files) for calls to unserialize() on user-supplied data, particularly around nonce validation
    Affected if Code contains unserialize() calls on $_POST, $_GET, or similar user input without proper sanitization
  4. Identify if nonces are properly validated
    Check the plugin code for wp_verify_nonce() calls and verify the nonce is being validated BEFORE any unserialize() call processes the data
    Affected if The nonce validation is missing, weak, or occurs after the vulnerable unserialize() call
  5. Check for active exploitation indicators
    Review web server access logs for requests to admin-ajax.php or admin-post.php with unusual serialized PHP objects in the POST data, or check for unexpected files in the /wp-content/uploads/ directory that may indicate RCE attempts
    Affected if Suspicious serialized payloads are found in logs or unexpected PHP files appear on the system

You are affected if the OptionTree plugin is installed and its version is below 2.7.0 and the plugin's admin settings functions contain unserialize() calls on user input.

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.0 or later
Fixed in 2.7.0
Interim mitigation

Update the OptionTree plugin to version 2.7.0 or later to remediate the object injection vulnerability.

Recommended fix High confidence

OptionTree version 2.7.0 or later

  1. Backup the WordPress site and database before making any changes
  2. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  3. Locate the OptionTree plugin in the list
  4. If an update to version 2.7.0 or later is available, click 'Update Now' to apply the fix
  5. If no automatic update appears, manually upload version 2.7.0 or later of the OptionTree plugin from the WordPress plugin repository
  6. After updating, verify the plugin version shows 2.7.0 or higher in the installed plugins list
  7. Review the plugin settings to ensure functionality is intact after the upgrade

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

Fix this in Optiontree Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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