Flag Forge CVE-2025-59932
HIGHAttack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessReach Flag Forge web endpoint
-
ExploitSend unauthenticated POST/DELETE to /api/resources
-
ExecutionBypass missing authz check
-
ImpactCreate, modify, or delete resources
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Access control enforcement
MITRE ATT&CK
1 technique across 1 tactic: Defense Evasion The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires only network reachability to the Flag Forge application's /api/resources endpoint on an instance running an affected version (2.0.0 through any release before 2.3.1); the attacker issues POST or DELETE requests with no credentials, because the endpoint previously performed no authentication or authorization check. Per CVSS AV:N/AC:L/PR:N/UI:N, there is no requirement for user interaction, prior authentication, or special configuration - it applies to default deployments of the vulnerable versions. The primary limiting factors are: the target must be an exposed/reachable Flag Forge instance in the vulnerable version range, and upgrading to 2.3.1 fully removes the condition. Impact is bounded to resource create/modify/delete (integrity, and availability via deletion); there is no confidentiality impact. |
| Impact | This is a broken access control flaw (CWE-284) in the Flag Forge CTF platform where the /api/resources endpoint accepted POST and DELETE requests without authentication or authorization. The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L, base 8.2) describes a network-reachable, low-complexity, unauthenticated issue with high integrity impact and low availability impact and no confidentiality impact - internally consistent with the description, which centers on unauthorized create/modify/delete of resources rather than data disclosure. However, the real-world exploitation signals point sharply downward: EPSS is only 0.06% (17th percentile), there is NO CISA KEV listing, and no public proof-of-concept was identified in the provided intelligence. The dominant risk-limiting factor is product footprint - Flag Forge is a niche open-source CTF platform, so even an easy-to-exploit, unauthenticated flaw affects very few production environments. Net assessment: a genuinely exploitable authorization gap with a plausibly high CVSS, but low practical priority outside of organizations actually running Flag Forge 2.0.0-2.2.x; those operators should patch to 2.3.1 promptly, while the broader population can treat this as low urgency. No signals conflict materially; the high CVSS reflects ease of access, not widespread or active exploitation. |
| Exploit ScenarioDerived | An attacker who can reach the Flag Forge web application sends an unauthenticated POST or DELETE request directly to the /api/resources endpoint, bypassing the intended login/role checks. Because no authentication or authorization is enforced, the attacker can create, tamper with, or delete platform resources - for example wiping or injecting CTF challenge resources during an event. No public exploit code was identified, but the attack is trivial to craft given the network vector and low complexity (AC:L, PR:N, UI:N). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv2 – Oct 09, 2026
Unauthenticated remote attackers can create, modify, or delete resources on Flag Forge CTF platform instances running versions 2.0.0 through any release before 2.3.1, because the /api/resources endpoint performed no authentication or authorization checks on POST and DELETE requests. The flaw is a broken access control issue (CWE-284, CVSS 8.2) requiring only network reachability to the endpoint on an affected, default deployment - no credentials, no user interaction, and no special configuration per the CVSS:3.1/AV:N/AC:L/PR:N/UI:N vector. Impact is limited to integrity and availability (resources can be tampered with or deleted, with no confidentiality impact), and no public exploit code or confirmed active exploitation has been identified at time of analysis; EPSS is low at 0.06% (17th percentile). The vendor has fixed the issue in Flag Forge 2.3.1.
Earlier versions of this analysis (1)
Flag Forge is a Capture The Flag (CTF) platform. Rated high severity (CVSS 8.6), this vulnerability is remotely exploitable, no authentication required, low attack complexity. No vendor patch available.
RemediationAI
Upgrade Flag Forge to version 2.3.1 or later, which the vendor advisory confirms removes the missing authentication/authorization check on /api/resources (GHSA-v8rh-25rf-gfqw, https://github.com/FlagForgeCTF/flagForge/security/advisories/GHSA-v8rh-25rf-gfqw); this is the only complete fix. Where an immediate upgrade is not possible, compensating controls should target the exposed write methods: block or restrict POST and DELETE to /api/resources at a reverse proxy or WAF so that only trusted administrative networks or authenticated sessions reach it (trade-off: legitimate administrative UI workflows that rely on those methods will also be blocked and must be re-allowed selectively); require HTTP authentication at the edge for the /api path (trade-off: adds a second credential layer that users of the CTF front end may find intrusive and that must be kept in sync with the app); and limit network exposure of the Flag Forge instance to trusted networks or a VPN rather than the public internet (trade-off: reduces the accessibility expected of a public CTF platform). None of these controls repair the underlying authorization defect, so upgrading to 2.3.1 should be scheduled regardless.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Flag Forge is a Capture The Flag (CTF) platform, and the affected component is its REST API, specifically the /api/resources route handled by the application's backend. The root cause is CWE-284 (Improper Access Control): the resource-management handlers for POST and DELETE accepted requests without verifying an authenticated session or an appropriate authorization role, effectively turning a privileged write/delete operation into an anonymous one. Because the request path is exposed over HTTP/HTTPS on the application itself, any party who can reach the Flag Forge instance can invoke it directly. The CPE string cpe:2.3:a:flagforge:flagforge:*:*:*:*:*:*:*:* confirms the vendor/product namespace affected, and the version wildcard corresponds to the 2.0.0-before-2.3.1 range called out in the GitHub Security Advisory. Per the assessed vector (C:N/I:H/A:L), the defect does not leak data but permits high-integrity modification plus some availability loss through deletion of resources.
Know when Flagforge gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
Endpoint is network-reachable with no auth check (AV:N/AC:L/PR:N/UI:N); unauthorized create/modify is high integrity, deletion gives low availability, and no data disclosure means C:N.
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
3DescriptionNVD
Flag Forge is a Capture The Flag (CTF) platform. From versions 2.0.0 to before 2.3.1, the /api/resources endpoint previously allowed POST and DELETE requests without proper authentication or authorization. This could have enabled unauthorized users to create, modify, or delete resources on the platform. The issue has been fixed in FlagForge version 2.3.1.
Executive ViewAI
Flag Forge CTF platform instances running versions 2.0.0 through any release before 2.3.1 are exposed to unauthenticated remote attackers who can create, modify, or delete resources via the /api/resources endpoint, disrupting competitions and training environments. Leadership should care because this undermines the integrity and availability of a platform often used for security training, recruiting, and public events, potentially causing reputational damage and operational disruption. No public exploit identified at time of analysis, but network-reachable default deployments remain at risk until upgraded to 2.3.1.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Affected Products (CPE)NVD
Flag Forge is a Capture The Flag (CTF) platform. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
Data exposure and unauthorized badge-template creation in FlagForge versions 2.0.0 through 2.3.1 allow remote unauthenti
Flag Forge is a Capture The Flag (CTF) platform. Rated high severity (CVSS 7.6), this vulnerability is remotely exploita
Flagforge versions 2.3.2 and earlier suffer from a Regular Expression Denial of Service (ReDoS) vulnerability in the use
Flag Forge is a Capture The Flag (CTF) platform. Rated medium severity (CVSS 6.9), this vulnerability is remotely exploi
Flag Forge is a Capture The Flag (CTF) platform. Rated high severity (CVSS 7.5), this vulnerability is remotely exploita
Flag Forge is a Capture The Flag (CTF) platform. Rated critical severity (CVSS 9.8), this vulnerability is remotely expl
NVD
CVE.org
EPSS
GitHub
Exploit-DB