# CVE-2025-54390: Cross-site request forgery in n/a

> Attackers can force password resets via CSRF if password reset features are enabled, leading to account takeover.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2025
- **Updated:** 17 Sep 2025
- **Also known as:** GHSA-mrjw-fxfc-2587

## What is CVE-2025-54390?

CVE-2025-54390 is a medium-severity vulnerability in n/a, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A Cross-Site Request Forgery (CSRF) vulnerability exists in the ResetPasswordRequest operation of Zimbra Collaboration (ZCS) when the zimbraFeatureResetPasswordStatus attribute is enabled. An attacker can exploit this by tricking an authenticated user into visiting a malicious webpage that silently sends a crafted SOAP request to reset the user's password. The vulnerability stems from a lack of CSRF token validation on the endpoint, allowing password resets without the user's consent.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2025-54390 being exploited?

There is no known exploitation of CVE-2025-54390 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54390 is a medium-severity vulnerability in n/a, published on 17 Sep 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-54390 in the wild and no public exploit code.

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

## Sources

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

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