FlagForge Allows Unauthenticated Badge Template API Access
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| FlagForgeCTF | flagForge | affected |
|
No data.
| Vendor | Product | Versions |
|---|---|---|
| Flagforgectf | Flagforge | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-32560 | 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. |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.451% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Flagforge
Flagforge flagforge |
|
| CPEs | cpe:2.3:a:flagforge:flagforge:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Flagforge
Flagforge flagforge |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Flagforgectf
Flagforgectf flagforge |
|
| Vendors & Products |
Flagforgectf
Flagforgectf flagforge |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | FlagForge Allows Unauthenticated Badge Template API Access | |
| Weaknesses | CWE-200 CWE-284 CWE-306 |
|
| References |
| |
| Metrics |
cvssV3_1
|