Skip to content
Web

CVE-2026-66594

8.5
High
EPSS 0.34%Aug 21, 2026

SQL injection in Persistent Login WordPress plugin (<=3.1.0) enabling DB compromise.

common questions

Is CVE-2026-66594 being exploited?

Not confirmed. CVE-2026-66594 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-66594?

CVE-2026-66594 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-66594?

Not known from our data. No patch reference has been recorded for CVE-2026-66594, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-66594 affect?

CVE-2026-66594 affects WordPress Persistent Login plugin <= 3.1.0, WordPress sites with the plugin installed. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-66594?

Apply vendor patch when released or remove/disable plugin; audit DB and logs.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPress Persistent Login plugin <= 3.1.0WordPress sites with the plugin installed
impact

Subscriber-level SQL injection allowing attackers to execute arbitrary SQL: data exfiltration, auth bypass, and full site/database compromise.

action required

Patch when possible

affected versions
lukeseager WordPress Persistent Login
  • affected<= 3.1.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free