# CVE-2026-62361: SQL injection in listmonk

> Authenticated users can exploit SQL injection in the export API to read sensitive database tables and modify data, exposing admin credentials.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2026
- **Updated:** 16 Jul 2026
- **Also known as:** GHSA-xgjr-7j9q-2h4r

## What is CVE-2026-62361?

CVE-2026-62361 is a medium-severity SQL injection vulnerability in knadh listmonk, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

listmonk is a standalone, self-hosted, newsletter and mailing list manager. Prior to 6.2.0, listmonk’s GET /api/subscribers/export endpoint injects the user-controlled query parameter into QuerySubscribersForExport in internal/core/subscribers.go without calling validateQueryTables, unlike GET /api/subscribers, allowing an authenticated user with subscribers:sql_query and subscribers:get_all to read arbitrary database tables such as users and settings and execute data-modifying PostgreSQL CTEs. This issue is fixed in version 6.2.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-62361?


## How do I fix CVE-2026-62361?

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

## Is CVE-2026-62361 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62361 and fix it if it is affected.

What it is: CVE-2026-62361 is a medium-severity SQL injection vulnerability in knadh listmonk, published on 15 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62361 exists.

Affected product: knadh listmonk. 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-2026-62361/ (Markdown: https://insights.sbomify.com/CVE-2026-62361/index.md)
```

## Sources

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

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