CVE-2026-18752 Persistent Login <= 3.1.0 - Authenticated (Subscriber+) SQL Injection via 'wppl_device_id' Cookie
Authenticated attackers can exploit SQL injection in the Persistent Login plugin to extract sensitive database information when the Login History feature is enabled.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-18752?
CVE-2026-18752 is a medium-severity SQL injection vulnerability in lukeseager Persistent Login, published on 1 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
The Persistent Login plugin for WordPress is vulnerable to generic SQL Injection via 'wppl_device_id' Cookie in all versions up to, and including, 3.1.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with subscriber-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. This vulnerability is only exploitable when the plugin's Login History feature is enabled.
Weakness: CWE-89
Which versions are affected by CVE-2026-18752?
How do I fix CVE-2026-18752?
No fix has been published for CVE-2026-18752 yet. Limit exposure of the affected software until one is available.
Use parameterised queries everywhere and never build SQL by joining strings. Upgrade affected software first; a web application firewall only buys time. More about SQL injection.
Is CVE-2026-18752 being exploited?
There is no known exploitation of CVE-2026-18752 in the wild and no public exploit code.
Sources
Also known as GHSA-9vm5-hh7p-3w4x.