SQL Injection in listmonk (CVE-2026-62361)
Summary
SQL injection in listmonk (CVE-2026-62361). Confidential information can be exposed externally. Exploitable via GET /api/subscribers/export.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-62361 has been found in listmonk.
Attackers can target a specific entry point like GET /api/subscribers/export over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "listmonk CVE-2026-62361" on the vendor's site.
CVE-2026-62361 (listmonk) — CWE-89 / CVSS v3 5.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/subscribers/export / GET /api/subscribers
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in listmonk. Attackers reach the vulnerable code path via GET /api/subscribers/export.
Check the vendor advisory for the affected versions of listmonk. Attack surface: GET /api/subscribers/export / GET /api/subscribers.
Severity: Medium (CVSS 5.5/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/subscribers/export requests with malformed payloads or SQL meta-characters. Run grep -r 'listmonk' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'listmonk' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
listmonkを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/subscribers/export' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/subscribers/exportへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against GET /api/subscribers/export on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com
- web github.com