listmonk: SQL Injection in /api/subscribers/export bypasses table access control, leaking admin password hashes and SMTP credentials
CVE-2026-62361GHSA-xgjr-7j9q-2h4r
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/knadh/listmonk 1.1.1-0.20260619102436-c0a6525009a6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 1.1.1-0.20260619102436-c0a6525009a6
- Fixed in
- 1.1.1-0.20260619102436-c0a6525009a6
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xgjr-7j9q-2h4r lists affected ranges: Go github.com/knadh/listmonk >=0 <1.1.1-0.20260619102436-c0a6525009a6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-xgjr-7j9q-2h4r lists affected ranges: Go github.com/knadh/listmonk >=0 <1.1.1-0.20260619102436-c0a6525009a6 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
- EPSS
- CVE-2026-62361: 0.30% estimated exploitation activity in the next 30 days; percentile 22.52 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary A SQL injection vulnerability in `GET /api/subscribers/export` allows an authenticated user with the `subscribers:sql_query` permission to bypass the table access control that exists on the regular query endpoint (`GET /api/subscribers`) and read arbitrary tables from the database — including `users` (bcrypt password hashes) and `settings` (SMTP credentials, API keys). Both error-based and time-based exfiltration techniques are confirmed to work. This creates a privilege escalation path: `subscribers:sql_query` → hash exfiltration → offline bcrypt crack (cost factor 6) → Super Admin account takeover. ---
Details The subscriber query feature accepts a user-controlled `query` parameter that is injected directly into a SQL template via `strings.ReplaceAll`. The regular query endpoint `GET /api/subscribers` correctly calls `validateQueryTables` to block access to sensitive tables before execution. The export endpoint `GET /api/subscribers/export` **omits this call…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-xgjr-7j9q-2h4r
- Revision 1 · created ·
Published from ghsa record GHSA-xgjr-7j9q-2h4r
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-62361 Advisory: listmonk: SQL Injection in `/api/subscribers/export` bypasses table access control, leaking admin password hashes and SMTP credentials IDs: CVE-2026-62361, GHSA-xgjr-7j9q-2h4r Record: https://patchnext.com/advisories/cve-2026-62361 (revision 2, source checked 7 Nov 2026, 06:05 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.5) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/knadh/listmonk 1.1.1-0.20260619102436-c0a6525009a6. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/knadh/listmonk: affected < 1.1.1-0.20260619102436-c0a6525009a6; fixed in 1.1.1-0.20260619102436-c0a6525009a6 ## Suggested inspection (read-only) - Go github.com/knadh/listmonk: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/knadh/listmonk. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-xgjr-7j9q-2h4r (GitHub-reviewed advisory GHSA-xgjr-7j9q-2h4r lists affected ranges: Go github.com/knadh/listmonk >=0 <1.1.1-0.20260619102436-c0a6525009a6) - Verified: https://osv.dev/vulnerability/GHSA-xgjr-7j9q-2h4r (OSV record GHSA-xgjr-7j9q-2h4r lists affected ranges: Go github.com/knadh/listmonk >=0 <1.1.1-0.20260619102436-c0a6525009a6 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…