{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59932 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59932 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59932 is a high-severity missing authorization vulnerability in FlagForgeCTF flagForge, published on 27 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-59932 and fix it if it is affected.\n\nWhat it is: CVE-2025-59932 is a high-severity missing authorization vulnerability in FlagForgeCTF flagForge, published on 27 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-59932 in the wild and no public exploit code.\n\nAffected product: FlagForgeCTF flagForge. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-59932/ (Markdown: https://insights.sbomify.com/CVE-2025-59932/index.md)","id":"CVE-2025-59932","markdown":"https://insights.sbomify.com/CVE-2025-59932/index.md","name":"CVE-2025-59932","record":{"aliases":["GHSA-v8rh-25rf-gfqw"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CTF platform","requires_auth":"none","summary":"Unauthenticated attackers can create, modify, or delete resources on the FlagForge CTF platform due to missing authorization checks.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flagforge","vendor":"flagforge"}],"cvss":{"score":8.6,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"FlagForgeCTF Unauthenticated Resource Modification/Deletion","id":"CVE-2025-59932","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"libvips is vulnerable to Buffer Over-Read in poppler-based pdfload","id":"CVE-2025-59933"},"packages":[],"prev":{"headline":"Not used","id":"CVE-2025-59930"},"products":["flagForge"],"published":"2025-09-27","related":[{"cvss_score":9.8,"headline":"FlagForgeCTF's Improper Session Handling Allows Access After Logout","id":"CVE-2025-59841","kev_date_added":null,"published":"2025-09-25"},{"cvss_score":9.4,"headline":"FlagForge Allows Unauthenticated Badge Template API Access","id":"CVE-2025-61777","kev_date_added":null,"published":"2025-10-06"},{"cvss_score":8.2,"headline":"FlagForgeCTF is Missing Authorization in main-v2","id":"CVE-2025-59827","kev_date_added":null,"published":"2025-09-24"},{"cvss_score":7.6,"headline":"FlagForgeCTF Vulnerable to Unauthorized Problem Creation","id":"CVE-2025-59826","kev_date_added":null,"published":"2025-09-23"},{"cvss_score":7.5,"headline":"Flag Forge has ReDoS Vulnerability in User Profile Lookup API","id":"CVE-2026-21868","kev_date_added":null,"published":"2026-01-08"},{"cvss_score":7.5,"headline":"FlagForgeCTF Hint Exposure via API","id":"CVE-2025-59833","kev_date_added":null,"published":"2025-09-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-29","vendors":["FlagForgeCTF"]},"summary":"Unauthenticated attackers can create, modify, or delete resources on the FlagForge CTF platform due to missing authorization checks.","url":"https://insights.sbomify.com/CVE-2025-59932/"}