dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-39499

HIGH · 7.2 CVSS v3.1 Published 2026-06-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Shop manager PHP Object Injection in Advanced Product Fields (Product Addons) for WooCommerce <= 1.6.19 versions.

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

PHP Object Injection vulnerability in Advanced Product Fields (Product Addons) for WooCommerce allows authenticated shop managers to inject serialized PHP objects, potentially executing arbitrary code via magic methods in the application ecosystem.

MitigationUpdate the plugin to a version newer than 1.6.19; if immediate update is not possible, restrict shop manager capabilities or disable the plugin until patched.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 Advanced Product Fields plugin version
    Navigate to Plugins > Installed Plugins in the WordPress admin dashboard, find 'Advanced Product Fields (Product Addons) for WooCommerce', and note the version number displayed. Alternatively, check the plugin's main PHP file header for the 'Version' tag.
    Affected if The installed version is 1.6.19 or earlier.
  2. Confirm the plugin is active
    In the WordPress admin under Plugins > Installed Plugins, verify that the plugin is currently activated. An inactive plugin would not be exploitable even if vulnerable.
    Affected if The plugin shows as 'Active' and the version is 1.6.19 or earlier.
  3. Check for shop manager user accounts
    In the WordPress admin under Users, review the list of users and identify any accounts with the 'Shop Manager' role. Only users with this role or higher privileges could trigger the vulnerability.
    Affected if At least one user account with Shop Manager role exists and the plugin version is 1.6.19 or earlier.
  4. Verify WordPress user capability for shop managers
    If users table is accessible via database, query the wp_usermeta table for meta_key = 'wp_capabilities' containing 'shop_manager' or 'administrator'. This confirms privilege level.
    Affected if Shop manager user accounts exist in the database and plugin version is 1.6.19 or earlier.

You are affected if the Advanced Product Fields (Product Addons) for WooCommerce plugin is active at version 1.6.19 or earlier and at least one Shop Manager user account exists on the site.

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

Update the plugin to a version newer than 1.6.19; if immediate update is not possible, restrict shop manager capabilities or disable the plugin until patched.

Recommended fix Moderate confidence

Version 1.6.20 or later (next available security release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate 'Advanced Product Fields (Product Addons) for WooCommerce'
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, download the updated plugin from a trusted source and upload via Plugins > Add New > Upload Plugin
  6. 6. After updating, verify the plugin version is greater than 1.6.19

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
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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