HomeWordPress vulnerabilitiesPersistent Login
Persistent Login vulnerabilities
Persistent Login has 3 known vulnerabilities in this database. The most recent published record is dated 30 Sep 2026.
- Known vulnerabilities
- 3
- Active installs
- 6,000+
- Latest version
- 3.1.4
- Last updated
- 26 Sep 2026
- Most recent
- 30 Sep 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-94081 | High 7.1 | Not yet published | Check for an update | 7 d ago |
| SQL injection CVE-2026-18752 | Medium 6.5 | Up to 3.1.0 | Fixed in a later version (latest 3.1.4) | 1 Sep 2026 |
| SQL injection CVE-2026-66594 | High 8.5 | Not yet published | Check for an update | 20 Aug 2026 |
Read the published descriptions
- CVE-2026-94081, 30 Sep 2026
- Unauthenticated Cross Site Scripting (XSS) in WordPress Persistent Login <= 3.1.3 versions. CVE record
- CVE-2026-18752, 1 Sep 2026
- 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 record
- CVE-2026-66594, 20 Aug 2026
- Subscriber SQL Injection in WordPress Persistent Login <= 3.1.0 versions. CVE record
What to do if you run Persistent Login
If you run Persistent Login, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Persistent Login vulnerabilities
Free. We email you when a new vulnerability is published for Persistent Login, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.