CVE-2026-19914: Security vulnerability
CVE-2026-19914 affects The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all up to, and i The Welcart e-Commerce plugin for WordPress. The published description indicates a remote...
What happened
A security weakness in The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all is being tracked as CVE-2026-19914. CVE-2026-19914 affects The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all up to, and i The Welcart e-Commerce plugin for WordPress. CVE-2026-19914 currently carries a HIGH 7 2 severity signal in the retained vulnerability data.
The available advisory information identifies up to, and i The Welcart e-Commerce plugin for WordPress as affected versions. The injected payload is delivered via. The published description indicates a remote or untrusted-network exploitation path.
Editorial note: this News Brief follows the available evidence and adds length only when additional facts or useful context are available. Where public reporting does not establish a specific victim sequence, CyberDeltaForce does not present one as fact.
What the reporting and advisory establish
1 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.
CVE-2026-19914 currently carries a HIGH 7.2 severity signal in the retained vulnerability data.
The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all versions up to, and including, 2.12.1 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 injected payload is delivered via
What this means for your environment
Move from the published facts to the technical path, exposure conditions and defensive decisions that matter in a real environment.
Attack & Exploitation Path
The sequence below shows how the vulnerability can be reached and what successful exploitation can produce. Each stage is labeled by evidence status.
Required condition: an affected The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all up to, and i The Welcart e-Commerce plugin for WordPress instance is reachable from a network position available to the attacker.
attacker-controlled network input reaches the vulnerable function on the affected The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all service.
the reported cross-site scripting is triggered inside The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all, crossing the security boundary described by the advisory or vulnerability record.
Not publicly disclosed in enough detail to state a specific post-exploitation result without inference.
Identify remotely reachable The Welcart e-Commerce plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'custom_order' parameter in all up to, and i The Welcart e-Commerce plugin for WordPress; remove unnecessary exposure; apply the vendor fix or mitigation; then review service, network and identity telemetry for exploitation attempts or unexpected follow-on activity.
Why this matters to you
CVE-2026-19914 matters because the practical risk is not the score alone — it is whether the affected technology or service up to, and including, 2 exists in your environment and whether the reported trigger or exposure path can reach it. The current severity is HIGH 7.2. No exploitation flag is currently present in the CDF data, but that does not remove the need to validate affected systems.
Does this deserve attention in my environment?
Check the conditions below against your use of the affected technology or service up to, and including, 2.
Select the conditions that are true in your environment. Leaving a condition unselected does not mean you are safe — it only means you have not marked it as applicable.
- Search endpoint, software and asset inventory for the affected technology or service up to, and including, 2.
- Confirm the vendor-recommended fixed version or mitigation and verify deployment, not just assignment, across affected assets.
- Review relevant endpoint, application, network or identity telemetry for activity associated with exploitation of the affected component.
- Track vendor and government guidance for any change in exploitation status while remediation is underway.
What remains unconfirmed
- Available reporting does not currently indicate exploitation, but that can change as vendor, government or threat-intelligence reporting develops.
Sources & References
Original reporting and technical references are kept here for readers who want to verify the facts. Publisher names stay out of the reading flow above.