SLICEWP · CVE-2026-120043 · Package
FIX → 1.2.15
The SliceWP Affiliates plugin for WordPress passes the 'email' parameter into an SQL query without proper escaping or preparation, in all versions up to and including 1.2.14. An unauthenticated attacker can append their own SQL queries to existing ones to read sensitive data from the site's database.
first public Nov 7, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
WordPress sites running the SliceWP Affiliates plugin (Affiliate Program Suite) version 1.2.14 or earlier. The injection is reached through the user_register hook on a WooCommerce My Account registration, using the 'email' value and a nonce any guest can get, so stores that let visitors register are the ones to look at first. Sites without the plugin, or on 1.2.15+, can skip it.
Not affected if patched-1.2.15, plugin-not-installed, woocommerce-registration-disabled
Who cares self-hosted, woocommerce, wordpress
Upgrade to 1.2.15
Update SliceWP Affiliates (slug slicewp) to 1.2.15 or newer.
The Affiliate Program Suite — SliceWP Affiliates plugin for WordPress is vulnerable to generic SQL Injection via the 'email' parameter in all versions up to, and including, 1.2.14 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The injection is reachable without any account because the vulnerable code path is triggered via the user_register hook fired on every successful WooCommerce My Account registration, which requires only a guest-obtainable nonce.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.