WordPress WordPress Persistent Login plugin <= 3.1.0 - SQL Injection vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps lukeseager/WordPress Persistent Login (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for lukeseager/WordPress Persistent Login.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 20, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 20, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 20, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress TheGem (Elementor) theme <= 5.12.3 - SQL Injection vulnerabilityAlso CWE-89
• WordPress Directory Pro plugin <= 2.5.8 - SQL Injection vulnerabilityAlso CWE-89
• WordPress Locatoraid Store Locator plugin <= 3.9.72 - SQL Injection vulnerabilityAlso CWE-89
• WordPress BookingPress Appointment Booking Pro plugin <= 6.0.2 - SQL Injection vulnerabilityAlso CWE-89
• WordPress WP w3all phpBB plugin <= 3.0.5 - SQL Injection vulnerabilityAlso CWE-89
• WordPress InfiniteWP Client plugin <= 1.13.9 - SQL Injection vulnerabilityAlso CWE-89