Editor-to-Administrator escalation via username collision
Published Jul 30, 2026 · Updated Jul 30, 2026
Authentication context confusion in Serendipity before 2.6.1 allows remote authenticated users to obtain Administrator privileges. The authentication path validates a password against one matching record, then serendipity_load_userdata performs a second username-only lookup and loads the first match. Editor access is required to rename an account to an Administrator's username; the next login with the Editor's password initializes an Administrator session and grants full administrative control.
Summary
What happened
Authentication context confusion in Serendipity before 2.6.1 allows remote authenticated users to obtain Administrator privileges. The authentication path validates a password against one matching record, then serendipity_load_userdata performs a second username-only lookup and loads the first match. Editor access is required to rename an account to an Administrator's username; the next login with the Editor's password initializes an Administrator session and grants full administrative control.
The record
- CVE
- CVE-2026-67351
- Published
- Jul 30, 2026
- Updated
- Jul 30, 2026
- Vendor
- Serendipity Team
- Product
- Serendipity
- Classifications
- CWE-287, CWE-304, T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 30, 2026CVE publishedPublication date reported by the CVE source.
- Jul 30, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <2.6.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream username-collision proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo