Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessForge ROBOT PAYMENT browser-return request
-
DeliveryEmbed malicious script in 'gid' parameter
-
ExploitPayload stored in order metadata
-
ExecutionAdministrator opens order in WP admin
-
ImpactScript executes in admin's authenticated 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 a WordPress site running Welcart e-Commerce version 2.12.5 or earlier with the ROBOT PAYMENT payment integration in use, because the payload is staged specifically through a forged ROBOT PAYMENT browser-return request that writes the attacker-controlled 'gid' value into order metadata. Staging the payload needs no authentication (PR:N). Execution is limited by a key precondition: a WordPress administrator must subsequently open the affected order in the admin panel for the stored script to fire - so impact depends on privileged-victim interaction and on the ROBOT PAYMENT flow being reachable, rather than firing automatically against all visitors. |
| Impact | This is a stored XSS (CWE-79) in the Welcart e-Commerce WordPress plugin, scored 7.2 (HIGH) by Wordfence with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N - the changed scope (S:C) and dual C:L/I:L reflect that injected script executes in a WordPress administrator's browser/session rather than only the attacker's context. PR:N confirms the staging step is reachable by an unauthenticated attacker. Exploitation status: no CISA KEV listing and no PoC or exploit reference appears in the input, so this is 'no public exploit identified at time of analysis'; the only external report is the Wordfence threat-intel advisory, which is not working exploit code. EPSS is not provided in the input, so probabilistic exploitation likelihood cannot be stated. The vuln.today decision label is 'this_week' (not act_now/emergency), consistent with a real but not top-tier priority. Conflicting signal worth verifying: the input vector carries UI:N, yet the description states the payload only fires 'when an administrator opens that order in the WordPress admin panel' - that is privileged-victim interaction, so the effective risk is gated by an admin viewing a maliciously-staged order; treat UI:N as optimistic and weigh the admin-interaction dependency when prioritizing. Overall: a genuine admin-targeting stored XSS that is unauthenticated to stage but conditioned on a specific payment integration and on admin interaction, rather than a wormable mass-exploitation issue. |
| Exploit ScenarioDerived | An unauthenticated attacker forges the ROBOT PAYMENT browser-return request to a site running Welcart e-Commerce (<= 2.12.5) with a malicious 'gid' value, which is stored unsanitized in order metadata. When a store administrator later opens that order in the WordPress admin panel, the injected script executes in the admin's authenticated session, enabling actions such as session/cookie theft or admin-context requests. No public exploit code is identified in the available sources at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 31, 2026
Stored cross-site scripting in the Welcart e-Commerce WordPress plugin through version 2.12.5 lets an unauthenticated visitor plant script in an order record by forging the ROBOT PAYMENT browser-return request with an arbitrary 'gid' value, which is written into order metadata without adequate sanitization or escaping. The injected script then executes in a WordPress administrator's browser when that order is opened in the admin panel, within that privileged session (changed scope, S:C). Affected sites are those running Welcart 2.12.5 or earlier with the ROBOT PAYMENT integration in use; the trigger therefore depends on a privileged victim opening the poisoned order, and no public exploit code was identified at time of analysis.
RemediationAI
Apply the upstream fix in changeset 3760784 (https://plugins.trac.wordpress.org/changeset/3760784/usc-e-shop), which sanitizes and escapes the affected 'gid' handling in trunk/functions/template_func.php, and update the Welcart e-Commerce plugin beyond 2.12.5; the input data does not state a tagged release version containing the fix, so confirm the installed plugin version after updating. The vendor advisory to track is https://www.wordfence.com/threat-intel/vulnerabilities/id/97e73872-bd1a-4b3a-9021-d0cd648456eb?source=cve. Until the update is verified, restrict the exposure described here: disable the ROBOT PAYMENT payment integration if it is not required (trading away that payment method), and limit or review administrative access to order screens so untrusted orders are opened only in a controlled session.
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
CWE-79: the 'gid' parameter arriving on the ROBOT PAYMENT browser-return path is stored in order metadata and later rendered into administrative order screens without sufficient input sanitization and output escaping. The vendor references point to code in the plugin's template_func.php, paymentJPayment.class.php and utility.php files at tag 2.12.5, with a fix changeset (3760784) modifying trunk/functions/template_func.php. The stored value crosses a trust boundary from an anonymous storefront request into the wp-admin context, which is why the score carries S:C with C:L/I:L; the trigger is limited to the ROBOT PAYMENT return flow and to an administrator subsequently viewing the affected order, and the sources do not describe any other exploitation path.
Know when Welcart E Commerce 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:N/S:C/C:L/I:L/A:N
Unauthenticated remote staging (AV:N/PR:N/AC:L) but execution needs a privileged admin to view the order (UI:R); S:C and C:L/I:L reflect script running in the admin's browser context, no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'gid' parameter in all versions up to, and including, 2.12.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The payload is staged by an unauthenticated visitor who forges the ROBOT PAYMENT browser-return request, storing the malicious gid value in order metadata; the script then fires when an administrator opens that order in the WordPress admin panel.
Executive ViewAI
A stored cross-site scripting vulnerability in Welcart (versions through 2.12.5) could let an attacker inject malicious code into order records via forged payment return requests. If an administrator opens a poisoned order, the attacker could execute scripts in the admin's browser, potentially compromising the entire WordPress site. This threatens e-commerce operations, customer data, and brand trust, and warrants immediate leadership attention.
No vendor-released patch identified at time of analysis. Interim mitigations include disabling the ROBOT PAYMENT integration, restricting admin access, deploying WAF rules to filter malicious 'gid' values, and manually reviewing order metadata for injected scripts.
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 Welcart E Commerce
View allThe Welcart e-Commerce WordPress plugin before 2.9.5 unserializes user input from cookies, which could allow unautehtnia
Unauth. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, low
The Welcart e-Commerce WordPress plugin before 2.9.5 does not validate files to be uploaded, as well as does not have au
The usc-e-shop (aka Collne Welcart e-Commerce) plugin before 1.9.36 for WordPress allows Object Injection because of usc
Stored cross-site scripting in the Welcart e-Commerce WordPress plugin (all versions before 2.11.34) allows any authenti
The Welcart e-Commerce plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on th
SQL injection in the Welcart e-Commerce WordPress plugin (all versions before 2.11.32) enables authenticated users holdi
The Welcart e-Commerce WordPress plugin before 2.8.4 does not have authorisation and CSRF in an AJAX action, allowing an
The Welcart e-Commerce WordPress plugin before 2.9.5 does not sanitise and escape a parameter before outputting it back
Session fixation in the Welcart e-Commerce WordPress plugin (all versions before 2.12.1) allows an unauthenticated remot
The Welcart e-Commerce WordPress plugin before 2.8.4 does not sanitise and escape some parameters, which could allow any
Payment callback fraud in the Welcart e-Commerce WordPress plugin (versions before 2.11.33) allows any unauthenticated r
EUVD-2026-114609
GHSA-8pvj-wmxx-5r34
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB