# CVE-2025-6517: Dromara MaxKey Meta URL SAML20DetailsController.java add server-side request forgery

> An attacker with permissions can exploit a server-side request forgery vulnerability in the SAML20 details controller to access internal resources.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2025
- **Updated:** 24 Jun 2025
- **Also known as:** GHSA-j5m6-wqrx-ch36

## What is CVE-2025-6517?

CVE-2025-6517 is a medium-severity server-side request forgery vulnerability in Dromara MaxKey, published on 23 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Dromara MaxKey up to 4.1.7 and classified as critical. This issue affects the function Add of the file maxkey-webs\maxkey-web-mgt\src\main\java\org\dromara\maxkey\web\apps\contorller\SAML20DetailsController.java of the component Meta URL Handler. The manipulation of the argument post leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-918 (Server-Side Request Forgery)

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

It affects 1 product.


Products: Maxkey Maxkey.

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

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

## Is CVE-2025-6517 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6517 is a medium-severity server-side request forgery vulnerability in Dromara MaxKey, published on 23 Jun 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-6517 exists.

Affected product: Dromara MaxKey. 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-6517/ (Markdown: https://insights.sbomify.com/CVE-2025-6517/index.md)
```

## Sources

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

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