{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-59843 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-59843 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-59843 is a medium-severity vulnerability in FlagForgeCTF flagForge, published on 26 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-59843 and fix it if it is affected.\n\nWhat it is: CVE-2025-59843 is a medium-severity vulnerability in FlagForgeCTF flagForge, published on 26 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-59843 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-59843/ (Markdown: https://insights.sbomify.com/CVE-2025-59843/index.md)","id":"CVE-2025-59843","markdown":"https://insights.sbomify.com/CVE-2025-59843/index.md","name":"CVE-2025-59843","record":{"aliases":["GHSA-qqjv-8r5p-7xpj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"CTF platform","requires_auth":"none","summary":"Attackers can retrieve user email addresses via a public API endpoint, exposing private user data.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"flagforge","vendor":"flagforge"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-359","name":"Exposure of Private Personal Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-09-27","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-09-27T02:55:20Z","kind":"github_poc","ref":"https://github.com/At0mXploit/CVE-2025-59843-CVE-2025-59932","stars":1,"title":"CVE on FlagForge on versions 2.0.0 to 2.3.0. Upgrade to version 2.3.1 to fix the issue."}],"tier":"poc_unverified"},"has_fix":false,"headline":"FlagForgeCTF Exposes User Emails via Public /api/user/[username] API","id":"CVE-2025-59843","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Argument injection vulnerability in SonarQube Scan Action","id":"CVE-2025-59844"},"packages":[],"prev":{"headline":"JupyterLab LaTeX typesetter links did not enforce `noopener` attribute","id":"CVE-2025-59842"},"products":["flagForge"],"published":"2025-09-26","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.6,"headline":"FlagForgeCTF Unauthenticated Resource Modification/Deletion","id":"CVE-2025-59932","kev_date_added":null,"published":"2025-09-27"},{"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-28","vendors":["FlagForgeCTF"]},"summary":"Attackers can retrieve user email addresses via a public API endpoint, exposing private user data.","url":"https://insights.sbomify.com/CVE-2025-59843/"}