dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-57390

MEDIUM · 6.5 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

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
Missing Authorization vulnerability in EDGARROJAS Extra Product Options Builder for WooCommerce additional-product-fields-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Extra Product Options Builder for WooCommerce: from n/a through <= 1.2.167.

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

A missing authorization vulnerability in the Extra Product Options Builder for WooCommerce plugin (additional-product-fields-for-woocommerce) allows authenticated users to access functionality beyond their intended privilege level due to incorrectly configured access control security levels. Attackers can exploit this to perform actions that should be restricted to higher-privilege users.

MitigationUpdate to the latest version of the plugin once available, or implement server-side access control restrictions at the web application firewall level to validate user permissions before allowing access to sensitive plugin endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 plugin installation directory
    Check your WordPress wp-content/plugins/ directory for a folder named 'additional-product-options-for-woocommerce', 'extra-product-options-for-woocommerce', or similar variations related to Extra Product Options functionality
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Identify the exact plugin folder name
    List all directories in wp-content/plugins/ that contain 'product-option' or 'extra-product' in the name and note the folder name used on your installation
    Affected if A folder matching the Extra Product Options plugin is found with any naming variant
  3. Read the installed plugin version
    Open the main PHP file in the plugin directory (usually the primary PHP file with the same name as the folder) and locate the 'Version:' header in the plugin comment block at the top of the file
    Affected if You can read the Version number from the plugin header
  4. Compare version against fixed release
    Check the WordPress plugin repository or the vendor changelog for the plugin to find when the authorization fix was released; compare your installed version to that release
    Affected if Your installed version is older than the version that includes the authorization fix
  5. Verify user role configuration
    Review your WordPress user roles and capabilities to identify which user roles have access to the plugin admin functionality (typically under WooCommerce > Product Options or similar menu items)
    Affected if Lower-privileged user roles (like Subscriber, Customer, or Contributor) have access to plugin admin features that should be restricted to Administrators only

You are affected if the Extra Product Options Builder for WooCommerce plugin is installed with a version that predates the security fix and your site allows user roles below Administrator to access plugin admin functions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the plugin once available, or implement server-side access control restrictions at the web application firewall level to validate user permissions before allowing access to sensitive plugin endpoints.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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