Vulnerability in Flagforge
CVE-2025-59843
Flag Forge is a Capture The Flag (CTF) platform. From versions 2.0.0 to before 2.3.2, the public endpoint /api/user/[username] returns user email addresses in its JSON response. The fix, intended for release in 2.3.1 but only available starting in version 2.3.2, removes email addresses from public API responses while keeping the endpoint publicly accessible. Users should upgrade to version 2.3.2 or later to eliminate exposure. There are no workarounds for this vulnerability.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N.
EPSS exploit prediction
EPSS 0.004, 36.2th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Flagforge
- Flagforgectf Flagforge — versions >= 2.0.0, < 2.3.2
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- At0mXploit/CVE-2025-59843-CVE-2025-59932 (1 star, last pushed 2025-09-27): CVE on FlagForge on versions 2.0.0 to 2.3.0. Upgrade to version 2.3.1 to fix the issue.
Also mentioned in 2 other repositories (fkie-cad/nvd-json-data-feeds, nomi-sec/PoC-in-GitHub). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/FlagForgeCTF/flagForge/security/advisories/GHSA-qqjv-8r5p-7xpj (Vendor Advisory)
- https://github.com/FlagForgeCTF/flagForge/commit/1b033f1b6e20fbf6df422d5d1afc9b2347528ace
- https://github.com/FlagForgeCTF/flagForge/compare/v2.3.1...v2.3.2
- https://github.com/FlagForgeCTF/flagForge/releases/tag/v2.3.1
This CVE has public exploit evidence. See the latest CVEs with public exploits.