dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-32457

MEDIUM · 5.3 CVSS v3.1 Published 2026-03-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in Wombat Plugins Advanced Product Fields (Product Addons) for WooCommerce advanced-product-fields-for-woocommerce allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Advanced Product Fields (Product Addons) for WooCommerce: from n/a through <= 1.6.18.

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

This is a Missing Authorization vulnerability in the Advanced Product Fields (Product Addons) for WooCommerce plugin. The plugin fails to properly enforce access control checks on certain functionality, allowing authenticated users (with low privileges) to access or manipulate product field configurations that should be restricted to administrators or higher-privileged roles. The vulnerability stems from incorrectly configured access control security levels that can be exploited to bypass authorization requirements.

MitigationUpdate the plugin to the latest version beyond 1.6.18 which should contain proper authorization fixes. If no update is available, implement proper capability checks and role-based access controls on all admin-facing functions, and restrict product field configuration operations to users with appropriate WooCommerce permissions.

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
None

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

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 plugin installation and version
    Locate the Advanced Product Fields (Product Addons) for WooCommerce plugin in your WordPress installation (typically in wp-content/plugins/advanced-product-fields or similar). Check the plugin header or main file for the declared version number.
    Affected if The installed version is 1.6.18 or lower, as versions beyond 1.6.18 contain the authorization fix.
  2. Confirm WooCommerce is active
    Verify that WooCommerce is installed and active on the WordPress site, as this plugin is a WooCommerce extension and requires WooCommerce to function.
    Affected if WooCommerce is not active - the vulnerability only applies when the plugin is fully functional within a WooCommerce environment.
  3. Review user role configuration
    Navigate to WordPress Users > Roles or use a role management plugin to examine which roles exist on the site. Check if the site allows user registration with subscriber or customer-level privileges.
    Affected if The site has subscriber, customer, or other low-privilege user roles enabled, as these roles can potentially exploit the missing authorization.
  4. Inspect product field admin capabilities
    Access the WooCommerce Products > Product Fields or similar admin menu item that manages product field configurations. Attempt to access this page with a low-privilege test account (subscriber or customer role).
    Affected if A low-privilege authenticated user can access or modify product field configurations without receiving an authorization error.
  5. Check for unauthorized field manipulation
    Using a low-privilege account, attempt to create, edit, or delete product field configurations through the plugin admin interface.
    Affected if Low-privilege users can successfully add, modify, or delete product field data that should be restricted to administrators only.

Your environment is affected if the installed plugin version is 1.6.18 or lower AND low-privilege authenticated users can access or manipulate product field configurations without proper authorization checks.

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 the plugin to the latest version beyond 1.6.18 which should contain proper authorization fixes. If no update is available, implement proper capability checks and role-based access controls on all admin-facing functions, and restrict product field configuration operations to users with appropriate WooCommerce permissions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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