Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level account
-
DeliveryCall save_meta_boxes to create AWL label
-
ExploitInject unescaped script into label content
-
ExecutionStore persists malicious payload
-
PersistVictim views rendered label
-
ImpactScript executes in victim browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires an authenticated WordPress account with Contributor-level capabilities or above on a site running the Advanced Woo Labels - Product Labels & Badges for WooCommerce plugin (version ≤2.51), because the 'save_meta_boxes' capability check is improperly secured rather than fully open. The attacker must be able to create an AWL product label, whose content is then rendered without proper escaping. Exploitation is limited by this authentication requirement (not unauthenticated) and by the fact that payload execution occurs only when a victim subsequently views a page rendering the malicious label. Note the plugin was only partially patched in 2.46, so even updated-but-pre-fix installs within the ≤2.51 range remain exposed. |
| Impact | This is a genuine-but-moderate authenticated stored XSS, not a high-urgency priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N = 5.4) shows network-reachable, low-complexity exploitation that nonetheless requires authenticated access at Contributor level or above (PR:L), which is the main gating factor - an attacker needs a valid low-privilege account on the WooCommerce store. No EPSS score, CISA KEV listing, or public proof-of-concept was provided in the intelligence; exploitation status is therefore 'no public exploit identified at time of analysis.' One notable conflict in the data: the vendor assigned S:U (scope unchanged), yet this is a stored XSS whose payload executes in the browsers of other users (store visitors and administrators who view the rendered labels), which typically warrants S:C and a score closer to 6.4 - this makes the official 5.4 arguably conservative. A second important signal: the description states the flaw was only 'partially patched in version 2.46' yet remains present in all versions 'up to, and including, 2.51,' meaning no fully-fixed release is confirmed in the provided data - defenders cannot simply 'update to patched version.' Net: real but bounded risk, limited by the Contributor+ authentication requirement. |
| Exploit ScenarioDerived | An attacker who holds or obtains a Contributor-level (or higher) account on a WooCommerce store calls the improperly-protected 'save_meta_boxes' function to create an Advanced Woo Labels product label containing a malicious script. Because the label content is rendered without proper output escaping, the stored script executes in the browser of anyone who views the affected product/store page - including shop visitors and administrators in the wp-admin context. No public exploit code was identified, and exploitation requires a valid authenticated low-privilege account. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Stored cross-site scripting in the Advanced Woo Labels - Product Labels & Badges for WooCommerce plugin (all versions up to and including 2.51) lets an authenticated attacker with Contributor-level access or higher create product labels whose content is written to the database and later rendered without proper output escaping. When a victim - an editor, administrator, or any site visitor viewing a page that renders the label - loads the affected page, the injected script executes in their browser session, enabling session theft, privilege escalation, or content manipulation within the WordPress context; the scoring is moderate (CVSS 5.4, adjusted to scope-changed at 5.x-class impact by this assessment) and no public exploit code or confirmed active exploitation was identified at time of analysis. Note that version 2.46 contained only a partial fix, so installs in the 2.47-2.51 range remain exposed.
RemediationAI
Upgrade the Advanced Woo Labels plugin to the latest release above 2.51 as soon as it is verified in the vendor changelog (https://kramakit.com/guide/free-version-changelog-awl/); do not treat version 2.46 as sufficient, since the vendor advisory and the independent assessment both note that 2.46 was only a partial patch and the improper capability check on 'save_meta_boxes' plus the unescaped label rendering persisted through 2.51 - a fix-version number above 2.51 is not confirmed in the available data, so validate the actual changelog entry before declaring a site remediated. If no complete fix is available for your version yet, apply compensating controls in this order: temporarily deactivate the plugin (eliminates exposure but removes all product labels site-wide and may break storefront layouts), restrict WP roles that carry label-editing capability by removing 'edit_posts'/'upload_files'-style label permissions from Contributor accounts via a role-management plugin or a map_meta_cap/user_has_cap filter (side effect: Contributors lose the ability to draft labels entirely), and review/audit existing awl label posts for injected <script>/event-handler markup and delete or sanitize any suspicious entries (side effect: legitimate labels with custom HTML may need re-authoring). Additionally, a WAF rule targeting <script or onerror=-style patterns in POST bodies to the WordPress admin-ajax/admin-post endpoints involved in label saving can reduce exposure, but WAF signature coverage for stored XSS is imperfect and should not replace patching. As defense in depth, enforce least privilege by minimizing the number of Contributor-and-above accounts on WooCommerce sites, keep WordPress core and WooCommerce current, and apply the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/a08d9118-3615-4f8e-a1cc-ba7e7873b7e5?source=cve for any updated guidance.
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 affected component is a WordPress plugin that registers custom product-label post types for WooCommerce and hooks into WordPress' meta-box save flow via a 'save_meta_boxes' handler (see the plugin's includes/admin/class-awl-admin.php around line 121). The root cause class is CWE-79 (Improper Neutralization of Input During Web Page Generation), arising from two compounding weaknesses: an improperly secured capability check on the save handler that does not correctly constrain who may persist label metadata, and the absence of context-appropriate escaping when that stored label content is emitted on the front end (label rendering paths in includes/class-awl-label-view.php and includes/class-awl-taxonomy.php). WordPress' security model depends on pairing a nonce/capability check on input with sanitization on save and escaping on output; here the capability check is insufficient and the output is unescaped, letting Contributor-level users - who normally cannot inject unfiltered HTML - store markup that is later executed as script in the browser of any higher-privileged user or visitor rendering the label. The plugin is distributed through the WordPress.org repository, so the entire installed base up to and including 2.51 is in scope per the published CPE (cpe:2.3:a:mihail-barinov:advanced_woo_labels_-_product_labels_&_badges_for_woocommerce). The CVSS 3.1 vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N reflects the initial NVD-style scoring (network-reachable, low-privilege authenticated, no user interaction, low confidentiality and integrity impact); the independent assessment raises the scope to Changed, which is more accurate for XSS because the injected script executes in the security context of the victim rather than the attacker.
Know when Wordpress Plugin 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:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Authenticated Contributor+ (PR:L) over network (AV:N/AC:L); stored XSS executes in other users' browsers so scope changes (S:C) with limited confidentiality/integrity impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Advanced Woo Labels - Product Labels & Badges for WooCommerce plugin for WordPress is vulnerable to unauthorized modification of data due to an improperly secure capability check on the 'save_meta_boxes' function in all versions up to, and including, 2.51. This makes it possible for authenticated attackers, with Contributor-level access and above, to create AWS labels that are rendered without proper escaping. The vulnerability was partially patched in version 2.46.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-90478
GHSA-4jg7-xq33-668f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB