dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-1929

HIGH · 8.8 CVSS v3.1 Published 2026-02-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Advanced Woo Labels plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 2.37. This is due to the use of `call_user_func_array()` with user-controlled callback and parameters in the `get_select_option_values()` AJAX handler without an allowlist of permitted callbacks or a capability check. This makes it possible for authenticated attackers, with Contributor-level access and above, to execute arbitrary PHP functions and operating system commands on the server via the 'callback' parameter.

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 Advanced Woo Labels WordPress plugin (versions up to 2.37) contains an insecure AJAX handler (`get_select_option_values()`) that uses `call_user_func_array()` with user-supplied input for both the callback function and its parameters. This allows any authenticated user with Contributor-level permissions or higher to invoke arbitrary PHP functions, leading to remote code execution on the underlying server.

MitigationUpgrade to the latest version of Advanced Woo Labels plugin (beyond 2.37) which should implement an allowlist of permitted callbacks and proper capability checks. If no update is available, disable the plugin until a patch is released.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if Advanced Woo Labels plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'advanced-woo-labels' or similar. In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and look for 'Advanced Woo Labels' or 'AWL' in the list.
    Affected if The plugin appears in the installed plugins list and the version is 2.37 or lower, or the version cannot be determined but the plugin name matches.
  2. Determine the installed plugin version
    If the plugin is found in the WordPress admin, click on the plugin name or view its details to read the Version number. Alternatively, open the main plugin PHP file (usually advanced-woo-labels.php or similar in the plugin folder) and look for a 'Version:' header in the plugin comments.
    Affected if The version listed is 2.37 or any version below 2.37, or no version information is visible but the plugin name matches.
  3. Verify the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if Advanced Woo Labels shows as 'Active' (not 'Inactive' or 'Must-Use').
    Affected if The plugin is active and meets the version condition above.
  4. Confirm the vulnerable AJAX handler exists
    Locate the AJAX handler file in the plugin directory (typically in includes/ or admin/ subfolders). Search for the function name 'get_select_option_values' and verify it uses call_user_func_array with unsanitized input. This typically appears in a file handling AJAX requests.
    Affected if The function get_select_option_values exists in the plugin code and uses call_user_func_array with user-supplied callback/parameters.
  5. Assess user access context
    Review WordPress user roles on the site (Users > All Users in admin). Determine if any users exist with Contributor, Author, Editor, or Administrator roles, as these roles have access to authenticated AJAX endpoints.
    Affected if Any authenticated user with Contributor-level permissions or higher exists on the site while the vulnerable plugin is active.

You are affected if Advanced Woo Labels plugin versions up to 2.37 is installed and active on your WordPress site, and the vulnerable AJAX handler with call_user_func_array exists in the codebase.

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

Upgrade to the latest version of Advanced Woo Labels plugin (beyond 2.37) which should implement an allowlist of permitted callbacks and proper capability checks. If no update is available, disable the plugin until a patch is released.

Recommended fix Moderate confidence

Advanced Woo Labels version 2.38 or later

  1. 1. Navigate to the WordPress admin dashboard and go to Plugins > Installed Plugins
  2. 2. Locate the 'Advanced Woo Labels' plugin in the list
  3. 3. Check if an update is available for the plugin
  4. 4. If an update is available, update the plugin to the latest version (version 2.38 or higher)

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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