Security readout for executives and security teams
Plain-English summary
CVE-2026-1929 affects the Advanced Woo Labels WordPress plugin for WooCommerce. An attacker with a Contributor-level account or higher could make the site run unintended server-side code. This can lead to full compromise of the website and underlying server context.
Executive priority
Treat as urgent for affected WooCommerce sites. The business risk is high because a low-privilege site account could become server-level code execution. Prioritize public stores and sites with many content contributors.
Technical view
The plugin’s get_select_option_values AJAX handler uses call_user_func_array() with user-controlled callback and parameters, without an allowlist or capability check. Sources describe remote code execution in versions up to and including 2.37. CVSS is 8.8, CWE-94, with low complexity and required authenticated low-privilege access.
Likely exposure
Exposure is limited to WordPress sites using Advanced Woo Labels – Product Labels & Badges for WooCommerce at version 2.37 or earlier, especially sites allowing Contributor-level users or compromised low-privilege accounts.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires authenticated access at Contributor level or above, but no user interaction is required after that access exists.
Researcher notes
Key evidence is the unsafe callback path in class-awl-admin-ajax.php and the Wordfence vulnerability entry. The provided affected metadata is inconsistent, but the CVE description and title state versions up to 2.37 are affected. No exploit-in-the-wild evidence is provided.
Mitigation direction
- Identify all WordPress sites using the Advanced Woo Labels plugin.
- Update the plugin if vendor guidance provides a fixed version.
- If no fix is available, disable or remove the plugin temporarily.
- Restrict Contributor and higher accounts to trusted users only.
- Review vendor and Wordfence advisories for updated remediation details.
Validation and detection
- Confirm installed Advanced Woo Labels versions across WordPress assets.
- Flag versions up to and including 2.37 for remediation.
- Review WordPress users with Contributor-level access or higher.
- Check site logs for suspicious admin-ajax activity involving callback parameters.
- Verify whether vendor guidance identifies a fixed release.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-1929 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/bbae9c33-becb-4c9d-917f-0d8fe8312d0c?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/advanced-woo-labels/tags/2.34/includes/admin/class-awl-admin-ajax.php#L136CVE reference
- https://plugins.trac.wordpress.org/browser/advanced-woo-labels/trunk/includes/admin/class-awl-admin-ajax.php#L146CVE reference
- https://plugins.trac.wordpress.org/browser/advanced-woo-labels/tags/2.37/includes/admin/class-awl-admin-ajax.php#L136CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.