Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain subscriber account
-
DeliverySubmit crafted field value with script payload
-
ExploitAdmin views injected content in dashboard
-
ExecutionScript executes in privileged session
-
ImpactSession hijack or account takeover
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 the WC Fields Factory plugin (version 4.1.12 or earlier) installed and active on a WordPress/WooCommerce site, AND an authenticated subscriber-level account under the attacker's control (PR:L). Exploitation is further gated on user interaction (UI:R): a victim - typically an administrator or staff user - must view the attacker-supplied field content for the stored/reflected script to execute. These two limiting factors (low-privilege authentication plus required victim interaction) substantially narrow realistic exploitation versus an unauthenticated, no-interaction flaw, despite the network attack vector. |
| Impact | This is a moderate-severity stored/reflected Cross-Site Scripting flaw (CVSS 6.5, CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L) in the WooCommerce add-on WC Fields Factory. The signals point to a real but conditional risk rather than a drop-everything priority. Positive risk factors: network attack vector (AV:N), low complexity (AC:L), and a changed scope (S:C) meaning the injected script executes in the context of other users/the broader WordPress session. Mitigating factors are significant: PR:L requires the attacker to already hold a valid low-privilege account (subscriber), and UI:R means a victim (typically an admin or another user) must view the malicious content for the payload to fire. No EPSS score, no CISA KEV listing, and no public exploit code were provided in the intelligence set - so there is no public exploit identified at time of analysis and no evidence of active exploitation. The 'Subscriber' qualifier in the title is consistent with the PR:L metric. Net assessment: a legitimate issue worth patching on a normal cadence, but the subscriber-account prerequisite plus required user interaction make opportunistic mass exploitation unlikely; the realistic threat is a malicious or compromised low-privilege user escalating against site operators. |
| Exploit ScenarioDerived | An attacker who has registered (or hijacked) a low-privilege subscriber account on a WooCommerce store running WC Fields Factory submits a crafted field value containing a JavaScript payload. When an administrator or other privileged user later views that data in the WordPress dashboard, the script executes in their browser context (scope change), potentially stealing session cookies or performing actions on their behalf. No public exploit code was identified in the provided data, so exploitation would require an attacker to develop the payload themselves. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 06, 2026
Stored/reflected cross-site scripting in WC Fields Factory 4.1.12 and earlier allows authenticated subscriber-level attackers to inject script that executes when a higher-privileged user views the affected field content. The plugin is a WooCommerce add-on for WordPress, and successful exploitation can lead to session theft, administrative actions performed in the victim's browser, or content manipulation, though the requirement for a subscriber account and victim interaction substantially narrows practical risk. CVSS 6.5; no public exploit identified at time of analysis, and no CISA KEV status is reported.
RemediationAI
No exact fixed version appears in the provided data, so check the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/wc-fields-factory/vulnerability/wordpress-wc-fields-factory-plugin-4-1-12-cross-site-scripting-xss-vulnerability?_s_id=cve and the WordPress plugin repository for an updated release, then upgrade WC Fields Factory beyond 4.1.12 once available. If no fixed version is available, disable or remove the WC Fields Factory plugin until a patch is published; this eliminates exposure but removes WooCommerce custom-field functionality. As compensating controls, restrict or monitor subscriber-level account creation so attackers cannot obtain the required low-privilege account, review existing subscriber accounts for suspicious activity, and consider a web application firewall rule targeting XSS payloads in WC Fields Factory requests. A Content Security Policy that blocks inline or unauthorized scripts can reduce execution risk, but may break legitimate plugin or site scripts and requires careful testing. Because exploitation also requires a victim to view attacker-supplied content, avoid clicking or previewing untrusted field submissions in administrative interfaces until patched.
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
WC Fields Factory is a WordPress plugin that extends WooCommerce with custom checkout, product, or order fields. The CPE cpe:2.3:a:saravana_kumar_k:wc_fields_factory:*:*:*:*:*:*:*:* identifies the Saravana Kumar K product family across versions, with the reported vulnerable range being 4.1.12 and earlier. CWE-79 (Improper Neutralization of Input During Web Page Generation, or Cross-site Scripting) is the root cause class: attacker-controlled input is not properly escaped or encoded before being included in HTML output. The CVSS vector AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L indicates the attack is network reachable, requires low privileges (an authenticated subscriber account), requires victim interaction, and has changed scope; impact is limited to low confidentiality, integrity, and availability. This aligns with a subscriber-accessible injection point where a victim with higher privileges must view the crafted field content for the script to execute.
Know when Wc Fields Factory 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:R/S:C/C:L/I:L/A:L
Subscriber account needed so PR:L; victim must render the payload so UI:R; XSS executes in another user's context giving S:C with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Subscriber Cross Site Scripting (XSS) in WC Fields Factory <= 4.1.12 versions.
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.
EUVD-2026-93249
GHSA-j6xp-vjqq-qcm8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB