CVE-2026-12417
Unauthenticated admin takeover via WordPress SignUp & SignIn plugin.
Can a WAF block it? Partly. The bug can be reached over the network, so generic WAF rules may stop some attacks. Its weakness type is unknown, so we cannot be more precise.
Also consider: patch
Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2026-12417 being exploited?
Not confirmed. CVE-2026-12417 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.82% probability of exploitation in the next 30 days.
How severe is CVE-2026-12417?
CVE-2026-12417 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-2026-12417?
Not known from our data. No patch reference has been recorded for CVE-2026-12417, 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-12417 affect?
CVE-2026-12417 affects WordPress SignUp & SignIn plugin (≤1.0.0). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-12417?
Upgrade to fixed version when available; rotate admin credentials; monitor for abuse.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can change any user's password via admin-ajax.php (pravel_change_password) and gain admin access.
Immediate action required
- affected<= 1.0.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.