Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious URL with XSS payload
-
DeliveryDeliver link to WooCommerce user via phishing
-
ExploitVictim clicks and parameter reflects unsanitized
-
ExecutionScript executes in victim browser
-
ImpactSteal session or perform actions as victim
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 | Exploitation requires an attacker to deliver a crafted link whose malicious parameter is reflected unsanitized by the PAYCOMET for WooCommerce plugin (versions n/a through 5.45), and requires a victim to click that link while the page is served - the UI:R metric confirms mandatory user interaction, which is the primary limiting factor. No authentication is required of the attacker per the vendor PR:N vector, but the payload only executes in the browser of the lured victim, so impact is scoped to that user's session on sites running the affected plugin. Realistic risk is further bounded by the need for a WooCommerce store to actually have this specific Spanish payment gateway installed and for a privileged user to be socially engineered into clicking. |
| Impact | This is a reflected cross-site scripting flaw (CWE-79) in the PAYCOMET for WooCommerce plugin, versions up to and including 5.45. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) indicates a network-reachable, low-complexity issue requiring no attacker privileges but requiring victim interaction (UI:R), with a scope change and only low impact to confidentiality, integrity and availability - a profile typical of reflected XSS where the payload executes in the victim's browser session rather than directly compromising the server. No EPSS score, CISA KEV listing, SSVC decision data, or public proof-of-concept was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The reflected (non-stored) nature means an attacker must lure a victim into clicking a crafted link, which lowers real-world risk relative to stored XSS or unauthenticated RCE; this is a moderate-priority patch-management item rather than an emergency. The A:L/I:L markings in the vendor vector are generous for a reflected XSS whose practical impact is browser-context script execution - treat the 7.1 as a conservative upper bound. |
| Exploit ScenarioDerived | An attacker crafts a URL pointing at a vulnerable PAYCOMET for WooCommerce page containing an unsanitized parameter that is reflected into the response, then delivers it to a logged-in store administrator or customer via phishing email or a malicious link. When the victim clicks it, the injected JavaScript executes in their browser in the context of the store's domain, enabling session/cookie theft or actions on their behalf. No public proof-of-concept was provided in the input. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 17, 2026
Reflected cross-site scripting in PAYCOMET for WooCommerce through version 5.45 allows a remote attacker to execute arbitrary script in a victim’s browser by luring them to a crafted URL that reflects an unsanitized parameter. The flaw requires user interaction and affects WordPress sites running this WooCommerce payment gateway; the attacker does not need credentials, but impact is limited to the victim’s session and the affected page. No public exploit code or CISA KEV entry was identified at time of analysis.
RemediationAI
Update PAYCOMET for WooCommerce to a release later than 5.45; the provided data does not specify an exact fixed version, so confirm the patched release in the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/paytpv-for-woocommerce/vulnerability/wordpress-paycomet-for-woocommerce-plugin-5-45-cross-site-scripting-xss-vulnerability?_s_id=cve). If an update is not immediately possible, reduce exposure by removing or disabling the plugin on sites that do not need the PAYCOMET gateway, deploy WAF rules that block script-bearing requests to the vulnerable parameter (tuning is required to avoid false positives), and enforce a restrictive Content-Security-Policy to limit inline script execution (testing is needed because CSP can break payment flows). Because exploitation requires a victim to click a crafted link, restrict untrusted links for privileged users and review logs for suspicious reflected payloads. Patch status: No vendor-released patch identified at time of analysis.
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 issue is CWE-79 (improper neutralization of input during web page generation) in a WordPress plugin that integrates the PAYCOMET payment gateway with WooCommerce. A request-controlled parameter is reflected into an HTML response without adequate output encoding, so script supplied in the URL executes in the context of the vulnerable site when a victim follows the link. The authoritative assessment scores this as CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N: network reachable, low attack complexity, no attacker authentication, mandatory victim interaction, scope changed because script runs in the victim's browser context, with limited confidentiality and integrity impact and no availability impact. CPE data was not provided; affected deployments are WordPress sites with the paytpv-for-woocommerce plugin installed.
Know when 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:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Reflected XSS is network-reachable with no privileges but requires victim interaction (UI:R); scope changes into the browser context (S:C) with low C/I impact and no genuine availability impact (A:N).
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in PAYCOMET PAYCOMET for WooCommerce paytpv-for-woocommerce allows Reflected XSS.This issue affects PAYCOMET for WooCommerce: from n/a through 5.45.
Articles & Coverage 1
Executive ViewAI
PAYCOMET for WooCommerce through version 5.45 carries a high-severity reflected cross-site scripting flaw that can run script in a victim’s browser after they follow a crafted URL, putting session data on affected WordPress/WooCommerce sites at risk. Vendor patch status is no vendor-released patch identified at time of analysis, and exploitation status is no public exploit identified at time of analysis, so leadership should focus on inventory and interim risk reduction for any site using this payment gateway. The business concern is checkout integrity and customer trust, not confirmed active exploitation.
No vendor-released patch identified at time of analysis. Interim mitigations include temporarily disabling or removing PAYCOMET for WooCommerce if not business-critical, deploying WAF/virtual patching rules to block reflected script payloads in request parameters, enforcing least privilege and monitoring checkout/session activity, and warning site administrators and users about crafted links.
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 Woocommerce
View allThe WooCommerce plugin through 3.x for WordPress has a Directory Traversal Vulnerability via a /wp-content/plugins/wooco
Unauthenticated arbitrary file upload in Addify's Request a Quote for WooCommerce plugin, affecting all versions up to a
The WooCommerce Help Scout WordPress plugin before 2.9.1 (https://woocommerce.com/products/woocommerce-help-scout/) allo
WooCommerce 7.1.0 contains a remote code execution vulnerability that allows attackers to execute arbitrary PHP code by
Unauthenticated path traversal in OrderConvo (the "Admin and Customer Messages After Order for WooCommerce" plugin), aff
Unauthenticated remote attackers can seize control of the payment configuration on WordPress stores running the Fundiin
Ultimate WooCommerce Gift Cards 3.0.2 is affected by a file upload vulnerability in the Custom GiftCard Template that ca
Unauthenticated attackers can exploit the Walletdoc Payment Gateway for WooCommerce plugin before version 1.8.5 to execu
Unauthenticated SQL injection in the ELEX WooCommerce Request a Quote WordPress plugin (all versions before 2.4.1) allow
Unauthenticated, network-reachable attackers can read the WooCommerce API consumer key and secret stored by the MgoSync
Unauth. Rated high severity (CVSS 7.5), this vulnerability is remotely exploitable, no authentication required, low atta
An issue was discovered in the NAB Transact extension 2.1.0 for the WooCommerce plugin for WordPress. Rated high severit
EUVD-2026-103285
GHSA-26h2-7xpc-qj48
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB