Persistent Login permits Subscriber-level SQL injection
Persistent Login through 3.1.0 uses the attacker-controlled wppl_device_id cookie in an insufficiently prepared SQL query. When Login History is enabled, a Subscriber or higher can append SQL and extract sensitive information from the WordPress database.
- Component
- Persistent Login
- Plugin slug
wp-persistent-login- Affected
- <= 3.1.0
- Safe version
- See mitigation notes
- Published
- Sep 01, 2026
This CVE was published Sep 01, 2026 and is one of 2 known issues for this plugin.
Update, patch or deactivate.
Update to a confirmed release newer than 3.1.0 when available. Until then, disable Login History when warranted, review Subscriber accounts and database activity, and rotate exposed secrets if exploitation is suspected.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical 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.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N