# CVE-2025-52841: Laundry 2.3.0 - Account Takeover via CSRF

> A CSRF vulnerability in Laundry allows attackers to take over user accounts via malicious requests.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **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:** 2 Jul 2025
- **Updated:** 2 Jul 2025
- **Also known as:** GHSA-m9gv-849c-fgw3

## What is CVE-2025-52841?

CVE-2025-52841 is a high-severity vulnerability in Laundry, published on 2 Jul 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

Cross-Site Request Forgery (CSRF) vulnerability in Laundry on Linux, MacOS allows to perform an Account Takeover. This issue affects Laundry: 2.3.0.

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

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

It affects 1 product.


Products: Laundry Project Laundry.

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

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

## Is CVE-2025-52841 being exploited?

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

## Other vulnerabilities in Laundry

- [CVE-2025-52842](https://insights.sbomify.com/CVE-2025-52842/): Laundry 2.3.0 - Account Takeover via Reflected XSS (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-52841 is a high-severity vulnerability in Laundry, published on 2 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-52841 exists.

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

## Sources

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

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