Skip to content
major vulnerability· requires attention

Unauthenticated admin escalation in a widely used WordPress plugin; could compromise many sites.

Web

CVE-2025-15027

9.8
Critical
EPSS 0.43%Feb 8, 2026

Privilege escalation in JAY Login & Register WP plugin allows unauthenticated admin access

common questions

Is CVE-2025-15027 being exploited?

Not confirmed. CVE-2025-15027 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.43% probability of exploitation in the next 30 days.

How severe is CVE-2025-15027?

CVE-2025-15027 is rated Critical with a CVSS score of 9.8. 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-2025-15027?

Not known from our data. No patch reference has been recorded for CVE-2025-15027, 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-2025-15027 affect?

CVE-2025-15027 affects WordPress JAY Login & Register plugin ≤ v2.6.03. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2025-15027?

Disable plugin; upgrade when patched; enable monitoring for abuse

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

executive summary
technical analysis
affected
WordPress JAY Login & Register plugin ≤ v2.6.03
impact

Unauthenticated attacker can elevate to administrator by updating arbitrary user meta via jay_login_register_ajax_create_final_user.

action required

Immediate action required

affected versions
jayarsiech JAY Login & Register
  • affected<= 2.6.03

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