CVE-2026-62361
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedlistmonk 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencelistmonk versions prior to 6.2.0 contain an SQL injection vulnerability in the GET /api/subscribers/export endpoint. This endpoint passes user-controlled query parameters directly to QuerySubscribersForExport without invoking validateQueryTables, unlike the similar GET /api/subscribers endpoint. An authenticated user with subscribers:sql_query and subscribers:get_all permissions can exploit this to read arbitrary database tables (e.g., users, settings) and execute data-modifying PostgreSQL CTEs.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed listmonk versionCheck the listmonk application version via its admin UI (Settings > About) or by querying the API at GET /api/health, or inspect the Docker image/tag if containerizedAffected if Version is lower than 6.2.0 (e.g., 6.1.x, 6.0.x, earlier versions)
-
Verify the /api/subscribers/export endpoint existsMake an authenticated GET request to /api/subscribers/export with a test query parameter (e.g., ?query=SELECT+1) and observe if it accepts the parameter without validationAffected if The endpoint accepts raw query parameters without triggering validation errors
-
Review user roles and permissionsIn listmonk admin UI, navigate to Users > Roles or query the backend database (table: roles or similar auth tables) to identify which roles have both subscribers:sql_query and subscribers:get_all permissions enabledAffected if Any user role has both subscribers:sql_query AND subscribers:get_all permissions granted
-
Check for suspicious API access patternsReview listmonk access logs or application logs for requests to GET /api/subscribers/export with unusual query patterns (e.g., UNION SELECT, information_schema, pg_ prefixes)Affected if Logs show requests to /api/subscribers/export containing SQL-like patterns or attempts to access system tables
-
Audit database user privilegesQuery the PostgreSQL database connected to listmonk: SELECT * FROM pg_user WHERE usename = 'listmonk'; to check if the listmonk database user has superuser or broad schema accessAffected if The listmonk database user has elevated privileges beyond what the application requires (e.g., superuser, schema-wide access)
-
Inspect recent database query logsEnable and review PostgreSQL logs (log_statement = 'all' or log_min_duration_statement) for queries originating from the listmonk application user that target tables outside the subscribers tableAffected if PostgreSQL logs show SELECT queries against non-subscribers tables (e.g., users, settings, campaigns) from the listmonk app user
The environment is affected if listmonk version is prior to 6.2.0 AND the /api/subscribers/export endpoint is accessible to users with subscribers:sql_query and subscribers:get_all permissions, or if logs show exploitation attempts.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade listmonk to version 6.2.0 or later which implements proper query validation. Until then, restrict or audit user permissions for subscribers:sql_query and monitor API access logs for unusual query patterns.
6.2.0
- Backup your listmonk database before proceeding with the upgrade
- Stop the running listmonk service
- Download listmonk version 6.2.0 from the official releases (github.com/knadh/listmonk/releases)
- Replace the existing listmonk binary with the new version 6.2.0 binary
- Restart the listmonk service
- Verify the application is running correctly and test the /api/subscribers/export endpoint to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-62361 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-62361 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data