# CVE-2025-61777: FlagForge Allows Unauthenticated Badge Template API Access

> Unauthenticated attackers can access and modify badge templates in FlagForge, leading to data exposure and database pollution.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Oct 2025
- **Updated:** 28 Jan 2026
- **Also known as:** GHSA-26rx-c53q-rjf9

## What is CVE-2025-61777?

CVE-2025-61777 is a critical missing authorization vulnerability in FlagForgeCTF flagForge, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### 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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-61777?

It affects 1 product.


Products: Flagforge Flagforge.

## How do I fix CVE-2025-61777?

No fix has been published for CVE-2025-61777 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-61777 being exploited?

There is no known exploitation of CVE-2025-61777 in the wild and no public exploit code.

Public exploit code:

- CVE on FlagForgeCTF  on versions v2.0.0 to v2.3.1. Upgraded to version 2.3.2 to fix the issue. (github_poc): https://github.com/0x0w1z/CVE-2025-61777

## Other vulnerabilities in FlagForgeCTF flagForge

- [CVE-2025-59841](https://insights.sbomify.com/CVE-2025-59841/): FlagForgeCTF's Improper Session Handling Allows Access After Logout (critical 9.8)
- [CVE-2025-59932](https://insights.sbomify.com/CVE-2025-59932/): FlagForgeCTF Unauthenticated Resource Modification/Deletion (high 8.6)
- [CVE-2025-59827](https://insights.sbomify.com/CVE-2025-59827/): FlagForgeCTF is Missing Authorization in main-v2 (high 8.2)
- [CVE-2025-59826](https://insights.sbomify.com/CVE-2025-59826/): FlagForgeCTF Vulnerable to Unauthorized Problem Creation (high 7.6)
- [CVE-2026-21868](https://insights.sbomify.com/CVE-2026-21868/): Flag Forge has ReDoS Vulnerability in User Profile Lookup API (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61777 and fix it if it is affected.

What it is: CVE-2025-61777 is a critical missing authorization vulnerability in FlagForgeCTF flagForge, published on 6 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-61777 in the wild and no public exploit code.

Affected product: FlagForgeCTF flagForge. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-61777/ (Markdown: https://insights.sbomify.com/CVE-2025-61777/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-61777
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-61777
- OSV: https://osv.dev/vulnerability/CVE-2025-61777

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-61777/
Summaries are generated and may contain mistakes; the official description above is the record.