CVE-2025-61777: FlagForgeCTF flagForge · Information Exposure
Affects FlagForgeCTF flagForgeSource CVE Database V5
Not known to be exploited · CVSS 9.4 Critical · fixed in 2.3.2 : patch FlagForgeCTF flagForge as a priority.
Data as of 26 Oct 2026, 12:29 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 38% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.2
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:LExploitation evidence
Disclosed: evidence found.
CVE published 6 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
The primary mitigation is to upgrade all affected FlagForgeCTF flagForge instances to version 2.3.2 or later, where authentication and authorization checks are properly enforced on all badge template endpoints. Organizations should audit their deployments to identify any running vulnerable versions (>=2.0.0 and <2.3.2) and prioritize patching. Network-level controls should be implemented to restrict access to administrative API endpoints, ideally limiting them to trusted internal networks or VPNs. Monitoring and logging access to these endpoints should be enabled to detect any anomalous or unauthorized activity. If immediate patching is not feasible, temporarily disabling or firewalling the `/api/admin/badge-templates` endpoints can reduce exposure, though this may impact platform functionality. Additionally, organizations should review badge template data for signs of unauthorized creation or modification and validate the integrity of their CTF platform data. Regular security assessments and penetration testing of CTF platforms are recommended to detect similar issues proactively.
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.