Critical · published October 6, 2025
🚨 A shocking oversight allowed any unauthorized user to access sensitive badge templates on Flag Forge! 🔥 Think of it like a library with no guard at the entrance — anyone can grab the rare manuscripts or even scribble in new titles without permission. That’s what’s happening here with the badge templates on the platform! An attacker could waltz in and not just steal sensitive metadata like 'created by' and 'updated at' dates but also create fake badge templates, polluting the database with garbage. This could lead to severe data exposure or even abuse of the badge system, which is absolutely devastating for any organization relying on it!
Think of it like a library with no guard at the entrance — anyone can grab the rare manuscripts or even scribble in new titles without permission. That’s what’s happening here with the badge templates on the platform! The vulnerability exists in the `/api/admin/badge-templates` GET and POST endpoints, which lacked proper authentication and authorization checks, allowing unauthorized access to sensitive badge information and the ability to create new templates.
An attacker could waltz in and not just steal sensitive metadata like 'created by' and 'updated at' dates but also create fake badge templates, polluting the database with garbage. This could lead to severe data exposure or even abuse of the badge system, which is absolutely devastating for any organization relying on it! Upgrade Flag Forge to version 2.3.2 or later immediately to secure those endpoints. Ensure that authentication is enforced and only admins can access or modify badge templates. There's no reliable workaround, so patching is a must! This vulnerability is fixable! Get that patch in place, and you’ll be back to hero status in no time! 🛡️
| Product | Versions | Fixed in |
|---|---|---|
| flagforge/flagforge | ≥ 2.0, < 2.3.2 | 2.3.2 |