CVE-2026-18752
Received Received - Intake

Persistent SQL Injection in WordPress Persistent Login Plugin

Publication date: 2026-09-01

Last updated on: 2026-09-01

Assigner: Wordfence

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-01
Last Modified
2026-09-01
Generated
2026-09-01
AI Q&A
2026-09-01
EPSS Evaluated
N/A
NVD
CVE-2026-18752
EUVD
EUVD-2026-68971

Affected Vendors & Products

Showing 2 associated CPEs
Vendor Product Version / Range
wordfence persistent_login to 3.1.0 (inc)
wp_persistent_login plugin to 3.1.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a SQL Injection flaw in the Persistent Login plugin for WordPress. It allows authenticated attackers with subscriber-level access or higher to inject malicious SQL queries via the 'wppl_device_id' cookie. The issue occurs due to insufficient input escaping and lack of proper SQL query preparation. Exploitation is only possible if the plugin's Login History feature is enabled.

Detection Guidance

Check WordPress sites using the Persistent Login plugin version 3.1.0 or below. Inspect HTTP requests for the 'wppl_device_id' cookie and look for suspicious SQL-like payloads in its value. Enable WordPress debug logs to monitor for database errors.

Impact Analysis

An attacker could exploit this to extract sensitive data from the WordPress database, such as user credentials, personal information, or other confidential data. This could lead to unauthorized access, data breaches, or further compromise of the WordPress site.

Compliance Impact

This vulnerability could lead to unauthorized data exposure, violating GDPR's data protection requirements or HIPAA's safeguards for protected health information. Organizations may face legal penalties, reputational damage, and loss of trust due to non-compliance resulting from a data breach.

Mitigation Strategies

Update the Persistent Login plugin to the latest version. Disable the Login History feature if enabled. Review database logs for unauthorized queries. Consider temporarily disabling the plugin until patched.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-18752. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart