جزئیات آسیب‌پذیری

Serendipity before 2.6.1 contains an authentication context confusion vulnerability where password validation and session loading operate independently without ensuring both use the same user record. An authenticated Editor can create a username collision with an Administrator account and obtain administrative privileges by logging in with their own password while the session loads the Administrator's account data.

• https://www.vulncheck.com/advisories/serendipity-authentication-bypass-via-username-collision third-party-advisory
• https://github.com/s9y/Serendipity/security/advisories/GHSA-v645-243f-jwgh vendor-advisory