Critical · published September 25, 2025
🚨 After logging out, users can still access protected areas of the Flag Forge platform! It’s like a restaurant letting diners keep their table after they’ve paid the bill — super surprising and definitely not secure! 🔥 Think of a library where you can still check out books even after your membership has expired. That’s exactly what’s happening here — the session remains active, allowing access to sensitive information like a VIP area without proper authorization. This vulnerability could be absolutely devastating! An unauthorized user could access protected endpoints, change profile data, or perform actions without logging in. Once logged out, they still hold the power to act as if they're authenticated, making it a prime target for exploitation.
Think of a library where you can still check out books even after your membership has expired. That’s exactly what’s happening here — the session remains active, allowing access to sensitive information like a VIP area without proper authorization. In versions 2.2.0 to just before 2.3.1, the Flag Forge web application fails to invalidate sessions upon logout, allowing authenticated users to access sensitive endpoints. CSRF tokens remain valid, which can lead to unauthorized actions.
This vulnerability could be absolutely devastating! An unauthorized user could access protected endpoints, change profile data, or perform actions without logging in. Once logged out, they still hold the power to act as if they're authenticated, making it a prime target for exploitation. Update Flag Forge to version 2.3.1 immediately to close this critical security gap. Additionally, review session management practices and CSRF token handling to ensure users are properly logged out. You've got this! Follow these steps and secure your platform in no time! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| flagforge/flagforge | ≥ 2.2, < 2.3.1 | 2.3.1 |