{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6099 exists.","fix":"No fix has been published for CVE-2025-6099 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-6099 is a medium-severity missing authorization vulnerability in szluyu99 gin-vue-blog, published on 16 Jun 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-6099 and fix it if it is affected.\n\nWhat it is: CVE-2025-6099 is a medium-severity missing authorization vulnerability in szluyu99 gin-vue-blog, published on 16 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6099 exists.\n\nAffected product: szluyu99 gin-vue-blog. 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-6099/ (Markdown: https://insights.sbomify.com/CVE-2025-6099/index.md)","id":"CVE-2025-6099","markdown":"https://insights.sbomify.com/CVE-2025-6099/index.md","name":"CVE-2025-6099","record":{"aliases":["GHSA-q7rg-mr58-3qfg"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Gin Vue Blog","requires_auth":"none","summary":"Attackers can bypass authorization checks in the PATCH request handler to perform unauthorized actions, requiring immediate attention from administrators.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"A vulnerability was found in szluyu99 gin-vue-blog up to 61dd11ccd296e8642a318ada3ef7b3f7776d2410. It has been declared as critical. This vulnerability affects unknown code of the file gin-blog-server/internal/manager.go of the component PATCH Request Handler. The manipulation leads to improper authorization. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used. This product is using a rolling release to provide continious delivery. Therefore, no version details for affected nor updated releases are available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"szluyu99 gin-vue-blog PATCH Request manager.go improper authorization","id":"CVE-2025-6099","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"realguoshuai open-video-cms list sql injection","id":"CVE-2025-6100"},"packages":[],"prev":{"headline":"UTT 进取 750W API setSysAdm strcpy buffer overflow","id":"CVE-2025-6098"},"products":["gin-vue-blog"],"published":"2025-06-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-06-16","vendors":["szluyu99"]},"summary":"Attackers can bypass authorization checks in the PATCH request handler to perform unauthorized actions, requiring immediate attention from administrators.","url":"https://insights.sbomify.com/CVE-2025-6099/"}