WooCommerce SagePay Direct Payment Gateway
sagepay-direct-for-woocommerce-payment-gateway · plugin
Known security vulnerabilities for WooCommerce SagePay Direct Payment Gateway. Find out in seconds which version runs on your site with WP Lens.
1 known vulnerabilities
latest Jul 2, 2014
Before you install
Do not install
- Closed on wordpress.org on Sep 20, 2014; no updates will come.
Do not install it on a new site; if it is installed, remove it or switch to a maintained alternative.
This assessment relies only on published vulnerability records and wordpress.org data; it does not review the code.
Is this component installed on your sites, and in which version? See it from inside the site with Noroxi Connector
Closed on wordpress.org
Removed from the directory on Sep 20, 2014 · reason: no reason given. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Nov 8, 2026
Vulnerabilities
- Medium 4.3
Multiple cross-site scripting (XSS) vulnerabilities in pages/3DComplete.php in the WooCommerce SagePay Direct Payment Gateway plugin before
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).
Exploited this week · every Monday
New KEV entries, fresh PoCs, WordPress triage and what to do this week. No account needed.