# CVE-2025-58430: listmonk Vulnerable to CSRF to XSS Chain That Can Lead to Admin Account Takeover

> Attackers can exploit a CSRF vulnerability combined with XSS to create unauthorized admin accounts in listmonk, leading to full system compromise.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/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:** Yes
- **Published:** 9 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-rf24-wg77-gq7w, GO-2025-3943

## What is CVE-2025-58430?

CVE-2025-58430 is a high-severity vulnerability in knadh listmonk, published on 9 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

listmonk is a standalone, self-hosted, newsletter and mailing list manager. In versions up to and including 1.1.0, every http request in addition to the session cookie `session` there included `nonce`. The value is not checked and validated by the backend, removing `nonce` allows the requests to be processed correctly. This may seem harmless, but if chained to other vulnerabilities it can become a critical vulnerability. Cross-site request forgery and cross-site scripting chained together can result in improper admin account creation. As of time of publication, no patched versions are available.

Weakness: CWE-80 (Improper Neutralization of Script-Related HTML Tags in a Web Page), CWE-79 (Improper Neutralization of Input During Web Page Generation), CWE-352 (Cross-Site Request Forgery)

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

3 open source packages ship an affected version, including github.com/knadh/listmonk. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/knadh/listmonk` | Go | All versions | None |
| `github.com/knadh/listmonk` | Go | All versions to 1.1.0 | None |
| `github.com/knadh/listmonk` | Go | All versions to 1.1.0 | None |

Products: Nadh Listmonk.

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

No fix published yet.

## Is CVE-2025-58430 being exploited?

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

## Other vulnerabilities in knadh listmonk

- [CVE-2025-49136](https://insights.sbomify.com/CVE-2025-49136/): listmonk's Sprig template Injection vulnerability leads to reading of Environment Variable for low privilege user (critical 9.1)
- [CVE-2026-34828](https://insights.sbomify.com/CVE-2026-34828/): listmonk: Active sessions remain valid after password reset and password change (high 7.1)
- [CVE-2025-46011](https://insights.sbomify.com/CVE-2025-46011/): SQL injection in n/a (medium 6.5)
- [CVE-2026-34584](https://insights.sbomify.com/CVE-2026-34584/): listmonk: Broken Access Control in CSV Import (Unauthorized List Assignment) (medium 5.4)
- [CVE-2026-21483](https://insights.sbomify.com/CVE-2026-21483/): listmonk Vulnerable to Stored XSS Leading to Admin Account Takeover (medium 5.4)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- github.com/knadh/listmonk (Go): affected all versions; no fix listed
- github.com/knadh/listmonk (Go): affected all versions up to 1.1.0; no fix listed
- github.com/knadh/listmonk (Go): affected all versions up to 1.1.0; no fix listed

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

## Sources

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

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