# CVE-2025-6099: szluyu99 gin-vue-blog PATCH Request manager.go improper authorization

> Attackers can bypass authorization checks in the PATCH request handler to perform unauthorized actions, requiring immediate attention from administrators.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2025
- **Updated:** 16 Jun 2025
- **Also known as:** GHSA-q7rg-mr58-3qfg

## What is CVE-2025-6099?

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.

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

Weakness: CWE-285 (Improper Authorization), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2025-6099 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6099 exists.

## Fix prompt for AI coding agents

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

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6099 exists.

Affected product: szluyu99 gin-vue-blog. 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-6099/ (Markdown: https://insights.sbomify.com/CVE-2025-6099/index.md)
```

## Sources

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

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