Vulnerability · Published Oct 6, 2025 · Assigned by GitHub_M
CVE-2025-61777FlagForge Allows Unauthenticated Badge Template API Access
Critical 9.4
In plain English
A critical-severity information exposure in flagForge from FlagForgeCTF. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.5% (higher than 39% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code.
Official description
Flag Forge is a Capture The Flag (CTF) platform. Starting in version 2.0.0 and prior to version 2.3.2, the `/api/admin/badge-templates` (GET) and `/api/admin/badge-templates/create` (POST) endpoints previously allowed access without authentication or authorization. This could have enabled unauthorized users to retrieve all badge templates and sensitive metadata (createdBy, createdAt, updatedAt) and/or create arbitrary badge templates in the database. This could lead to data exposure, database pollution, or abuse of the badge system. The issue has been fixed in FlagForge v2.3.2. GET, POST, UPDATE, and DELETE endpoints now require authentication. Authorization checks ensure only admins can access and modify badge templates. No reliable workarounds are available.
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| FlagForgeCTF | flagForge | >= 2.0.0, < 2.3.2 |
Weakness: CWE-200, CWE-284, CWE-306 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L