Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify exposed Trudesk with NODE_ENV unset
-
DeliverySend unauthenticated request to /debug/populatedb
-
ExploitDelete all groups, tags and tickets
-
ExecutionLog in with seeded 'password' account
-
ImpactTake over reset helpdesk instance
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V13 - Configuration Secure default settings
|
| Exploitation Conditions | Exploitation requires the Trudesk instance (≤1.2.11) to be running with the NODE_ENV environment variable unset - this leaves the /debug/* routes (notably /debug/populatedb) registered and reachable; a production deployment that sets NODE_ENV=production does not expose them, which is the primary limiting factor. When that condition holds, no authentication, no user interaction, and no special privileges are needed (PR:N/UI:N), and the attack works against the network-reachable HTTP interface. The destructive action is irreversible data loss (groups, tags, tickets), and follow-on access depends on the default seeded accounts still using the password 'password'. |
| Impact | Signals point to a credible but conditionally-gated destructive flaw rather than a top-tier emergency. The CVSS 4.0 vector (AV:N/AC:L/PR:N/UI:N) confirms remote, unauthenticated, no-interaction reachability, but AT:P (Attack Requirement: Present) encodes a real precondition - the debug routes are only exposed when NODE_ENV is unset. Reported by VulnCheck with a corroborating VulnCheck advisory and an independent HackMD technical write-up, the root cause and exploitation path are well-documented. No EPSS score, no CISA KEV listing, and no explicit POC flag were supplied in the input, so this is: no public exploit identified at time of analysis, and not confirmed actively exploited. Impact is integrity/availability only (VI:H/VA:H, VC:N): /debug/populatedb wipes groups, tags, and tickets and reseeds accounts whose password is 'password', enabling takeover of a reset instance. Note the apparent tension - the vendor vector sets VC:N (no confidentiality impact), yet logging in via the seeded 'password' account would in practice grant application access; the official vector attributes impact to the data-destruction primitive, not the post-reset login, so confidentiality is scored conservatively. Overall: real priority for any Trudesk operator running without NODE_ENV set to production, but the non-default configuration dependency and the product's niche footprint lower aggregate real-world risk versus a true 8.3-across-the-board flaw. |
| Exploit ScenarioDerived | An attacker locates an internet-exposed Trudesk helpdesk (≤1.2.11) started without NODE_ENV configured, so the /debug routes are live. They send an unauthenticated HTTP request to /debug/populatedb, destroying all groups, tags, and tickets and reseeding default accounts, then log in with a seeded account using the password 'password' to control the reset instance. A HackMD technical write-up documents the route and method, though no packaged exploit was indicated in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Unauthenticated remote attackers can wipe every group, tag and ticket in Trudesk 1.2.11 and earlier by calling the /debug/populatedb route, which remains registered whenever the NODE_ENV environment variable is unset - an unauthenticated, no-interaction, network-reachable action that destroys data integrity and availability (rated 8.3, CWE-1188) but is gated entirely by that deployment-configuration prerequisite rather than by any credential. The same call reseeds the database with default accounts whose password is 'password', so a successful wipe can additionally hand the attacker a working login to the emptied instance. No CISA KEV activity and no public exploit code were identified at time of analysis, and the overall signal is a credible but conditionally-gated destructive flaw rather than a top-tier emergency.
RemediationAI
No vendor-released patch was identified at time of analysis, so mitigation is configuration-first. Set NODE_ENV=production (or any truthy value) in the process environment before starting Trudesk - systemd Environment=, Docker ENV/-e, or the supervisor's env block - and then verify empirically that GET /debug/populatedb returns 404 rather than executing, since the check is evaluated at route-mount time and only takes effect after a restart. As defense in depth, block the prefix at the reverse proxy (e.g. nginx 'location ~ ^/debug/ { return 404; }' or an equivalent Traefik/ALB rule); the trade-off is that legitimate developers lose remote debug access, which is acceptable on production hosts. Because the destructive action is irreversible, also remove or change the default seeded accounts (the password 'password' is well known) and ensure current backups exist so a wipe can be recovered; restricting the web interface to a trusted network or VPN reduces exposure further. Detection: alert on any request to /debug/populatedb or other /debug/* paths in web-server and application logs - such requests from untrusted sources should be treated as an active destructive attempt. Consult https://www.vulncheck.com/advisories/trudesk-through-1.2.11-missing-authentication-on-debug-routes and the upstream repository https://github.com/polonel/trudesk for any subsequent fixed release before upgrading.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Trudesk is an open-source Node.js/Express helpdesk and ticketing application (vendor: polonel, CPE cpe:2.3:a:polonel:trudesk:*:*:*:*:*:*:*:*). The root cause is CWE-1188 (Insecure Default Initialization of Resource): the application mounts its diagnostic route group only when NODE_ENV is falsy, so a deployment that starts the process without NODE_ENV set - the default state for a naive 'npm start' or container launch - silently inherits development-only endpoints. Per the referenced source, the gating check lives in app.js (line 32) and the handlers themselves are defined in src/routes/index.js (lines 398-433), which include /debug/populatedb, a routine that clears and reseeds core collections (groups, tags, tickets) and default user accounts. No middleware on that router enforces session or role checks, so reachability of the Express HTTP interface is sufficient. The vendor's CVSS 4.0 vector (AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H) and our independent CVSS 3.1 assessment (AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:H) converge on the same picture: confidentiality is not directly exposed, integrity and availability are fully lost, and the 'attack requirements present' / high-complexity rating reflects exactly one precondition - the unset environment variable.
Know when Trudesk gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
Remote unauthenticated (AV:N/PR:N/UI:N); AC:H reflects the non-attacker-controlled NODE_ENV-unset precondition; impact is data destruction (I:H/A:H) with no confidentiality (C:N).
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Trudesk through 1.2.11 contains a missing authentication vulnerability in debug routes enabled whenever NODE_ENV is unset, letting unauthenticated attackers invoke them remotely. Attackers can call /debug/populatedb to delete all groups, tags and tickets, then log in with seeded accounts using the password 'password'.
Executive ViewAI
Trudesk 1.2.11 and earlier deployments with NODE_ENV unset are exposed to a destructive flaw that can erase all groups, tags, and tickets and reseed default accounts, causing service disruption, loss of ticket history, and potential unauthorized access to a reset instance. Leadership should prioritize inventory and containment because recovery could require emergency backups and credential cleanup, although no public exploit identified at time of analysis and the risk is gated by that deployment configuration.
No vendor-released patch identified at time of analysis. Set NODE_ENV to a non-empty value such as production on all Trudesk 1.2.11 and earlier instances and restart; block or restrict /debug/populatedb at the reverse proxy/WAF; limit Trudesk network exposure to trusted users; remove or disable debug routes where feasible; maintain and test offline backups; monitor for calls to /debug/populatedb and unexpected database resets; disable or rotate default accounts and enforce strong credentials.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Unrestricted Upload of File with Dangerous Type in GitHub repository polonel/trudesk prior to 1.2.4. Rated critical seve
Incorrect Use of Privileged APIs in GitHub repository polonel/trudesk prior to 1.2.4. Rated critical severity (CVSS 9.8)
Weak Password Requirements in GitHub repository polonel/trudesk prior to 1.2.2. Rated critical severity (CVSS 9.8), this
Execution with Unnecessary Privileges in GitHub repository polonel/trudesk prior to 1.2.3. Rated high severity (CVSS 8.8
Improper Privilege Management in GitHub repository polonel/trudesk prior to 1.2.2. Rated high severity (CVSS 8.8), this
Incorrect Synchronization in GitHub repository polonel/trudesk prior to 1.2.3. Rated high severity (CVSS 8.1), this vuln
Unrestricted Upload of File with Dangerous Type in GitHub repository polonel/trudesk prior to 1.2.2. Rated high severity
The trudesk application allows large characters to insert in the input field "Full Name" on the signup field which can a
Improper Restriction of Rendered UI Layers or Frames in GitHub repository polonel/trudesk prior to 1.2.2. Rated medium s
Use of Incorrect Operator in GitHub repository polonel/trudesk prior to 1.2.3. Rated medium severity (CVSS 6.5), this vu
Integer Overflow or Wraparound in GitHub repository polonel/trudesk prior to 1.2.2. Rated medium severity (CVSS 6.5), th
Allowing long password leads to denial of service in polonel/trudesk in GitHub repository polonel/trudesk prior to 1.2.2
EUVD-2026-107244
GHSA-fj4q-cf3c-rrp2
NVD
CVE.org
EPSS
Exploit-DB