CVE-2026-67351
Auth context confusion lets Editor account assume Administrator privileges via username collision.
Is CVE-2026-67351 being exploited?
Not confirmed. CVE-2026-67351 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.37% probability of exploitation in the next 30 days.
How severe is CVE-2026-67351?
CVE-2026-67351 is rated High. 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-67351?
Yes. A fix has been recorded for CVE-2026-67351. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67351 affect?
CVE-2026-67351 affects Serendipity CMS (< 2.6.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67351?
Upgrade to Serendipity 2.6.1 now; audit and restrict editor accounts.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated Editor can create a username collision to load an Administrator session and gain full admin control, enabling site takeover.
Immediate action required
- affected< 2.6.1
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.