Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify store running vulnerable plugin
-
DeliverySend unauthenticated AJAX request to exposed action
-
ExploitMissing capability/nonce check grants access
-
ExecutionDisclose or permanently delete obsolete product variations
-
ImpactIrrecoverable data loss and information disclosure
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the SKU Error Fixer for WooCommerce plugin (version through 1.0) installed and active on a WooCommerce store; the two vulnerable AJAX actions are registered for unauthenticated (nopriv) users and perform no capability or nonce checks, so no login or user interaction is needed. Exploitation is scoped and limited: the attacker can only disclose or delete product variations the plugin itself classifies as 'obsolete', not arbitrary products or site data, which is why Attack Complexity is High rather than Low. The practical impact ceiling is permanent, non-recoverable loss of those specific variations plus disclosure of their details. |
| Impact | Signals point to a genuine but low-priority issue. The CVSS 3.1 base score of 6.5 (AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N) reflects a network-reachable, unauthenticated flaw whose weight comes mainly from the I:H component (permanent, unrecoverable deletion), tempered by AC:H because the attacker only affects variations the plugin itself classifies as 'obsolete' rather than arbitrary data. Exploitation-probability signals are low and mutually consistent: EPSS is 0.14% (3rd percentile) and the CVE is NOT in CISA KEV, so there is no evidence of active exploitation. Publicly available exploit code exists (WPScan), which raises opportunistic risk but must not be conflated with active exploitation - PoC availability and in-the-wild use are distinct signals here. No SSVC decision data was provided in the input. The dominant risk-limiting factor is deployment footprint: this is an obscure WordPress/WooCommerce plugin at version 1.0, so even a trivially reachable unauthenticated bug has a very small real-world blast radius. Net: real and worth patching for anyone running the plugin, but not a broad emergency. |
| Exploit ScenarioDerived | An unauthenticated attacker finds a WooCommerce store running the SKU Error Fixer plugin (through 1.0) and sends a crafted AJAX request to one of its two unprotected actions. Because no capability or nonce checks are enforced, the request either discloses the details of product variations flagged as obsolete or permanently deletes them with no recoverable copy. Public exploit code for this flaw is available via WPScan, lowering the barrier to opportunistic abuse. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 09, 2026
Unauthenticated attackers can permanently delete product variations and read their details on WooCommerce stores running the SKU Error Fixer for WooCommerce plugin through version 1.0, because two of the plugin's AJAX actions lack both capability and nonce checks. Publicly available exploit code exists, and the deletions leave no recoverable copy behind, although the impact is scoped to variations the plugin itself classifies as obsolete rather than arbitrary products or site data. EPSS is low at 0.14% (3rd percentile) and there is no confirmed active exploitation (CISA KEV), so this rates as genuine but low-priority.
RemediationAI
No vendor-released patch or fixed version appears in the available intelligence, so the primary action is to deactivate and remove the SKU Error Fixer for WooCommerce plugin (through 1.0) from any production WooCommerce site; the side effect is loss of whatever SKU-mismatch detection and obsolete-variation cleanup the plugin provided, which must be handled manually or replaced. If the plugin cannot be removed immediately, block unauthenticated POSTs to /wp-admin/admin-ajax.php that carry this plugin's action parameters using a WAF or web-server rule - the trade-off is that broadly blocking nopriv admin-ajax traffic breaks front-end AJAX features of other plugins, so scope the rule to the specific action names. Because the delete action leaves no recoverable copy, take and verify full database backups (particularly wp_posts and wp_postmeta) before and after any exposure window, and audit WooCommerce variation tables for unexplained deletions. Also review the WPScan advisory at https://wpscan.com/vulnerability/889aaa2a-ad05-423a-a601-70ac1d8b7920/ for the affected action names and any updated guidance, and monitor https://nvd.nist.gov/vuln/detail/CVE-2026-86850 for a vendor fix; if a patched release is later published, upgrade to that exact version rather than relying on compensating controls.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-862 (Missing Authorization) in a WordPress plugin that registers two AJAX handlers via the wp_ajax_nopriv_ hook, making them reachable without authentication; neither handler calls current_user_can() for a capability check nor check_ajax_referer() for nonce verification. This is a classic WordPress plugin authorization gap: the nopriv registration is intended for front-end convenience but here lets any remote requester invoke routines designed for administrators. The plugin identifies WooCommerce product variations whose SKUs no longer match and treats them as 'obsolete'; the vulnerable actions then either disclose those variations' details or force-delete them. Because the deletion path appears to bypass the WooCommerce trash/restore workflow, the affected variation records and their postmeta are lost without a recoverable copy. The supplied CPE string (cpe:2.3:a:unknown:sku_error_fixer_for_woocommerce:*:*:*:*:*:*:*:*) is fully wildcarded with an unknown vendor, indicating the product is not formally registered in the NVD CPE dictionary and that version-level CPE matching is unreliable here; EUVD tracks the same issue as EUVD-2026-95503 with an affected range of 0 through 1.0.
Know when Sku Error Fixer For Woocommerce gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:H/A:N
Unauthenticated network-facing AJAX actions give AV:N/PR:N/UI:N; AC:H because impact is confined to plugin-classified 'obsolete' variations; C:L for detail disclosure and I:H for permanent unrecoverable deletion.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
3DescriptionCVE.org
The SKU Error Fixer for WooCommerce WordPress plugin through 1.0 does not perform any capability or nonce checks on two of its AJAX actions, which are also available to unauthenticated users, allowing them to permanently delete product variations it classifies as obsolete, and to disclose those variations' details, with no recoverable copy left behind.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-95503
GHSA-8gp3-27p2-m5q6
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB