Skip to content
Web

CVE-2026-12598

8.1
High
EPSS 0.56%Patch availableJul 10, 2026

Auth bypass in LoginPress Pro via unverified Spotify email allows account takeover.

common questions

Is CVE-2026-12598 being exploited?

Not confirmed. CVE-2026-12598 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.56% probability of exploitation in the next 30 days.

How severe is CVE-2026-12598?

CVE-2026-12598 is rated High with a CVSS score of 8.1. 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-12598?

Yes. A fix has been recorded for CVE-2026-12598. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-12598 affect?

CVE-2026-12598 affects WordPress sites using LoginPress Pro <=6.2.3, LoginPress Pro Spotify Social Login addon. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-12598?

Update LoginPress Pro and Spotify addon to fixed version or disable Spotify login immediately.

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

executive summary
technical analysis
affected
WordPress sites using LoginPress Pro <=6.2.3LoginPress Pro Spotify Social Login addon
impact

Unauthenticated attacker can log in as any WordPress user (including admins) by using a Spotify account with the victim's email.

action required

Immediate action required

affected versions
LoginPress LoginPress Pro
  • affected<= 6.2.3

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