CVE-2025-62713
Published: 23 October 2025
Summary
CVE-2025-62713 is a high-severity OS Command Injection (CWE-78) vulnerability. Its CVSS base score is 7.2 (High).
Operationally, ranked in the top 23.8% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis
Kottster, a self-hosted Node.js admin panel, contains a pre-authentication remote code execution vulnerability affecting versions 3.2.0 through 3.3.1 when the application runs in development mode. The flaw, tracked under CWE-78 and CWE-284, stems from insufficient access controls that permit unauthenticated command execution on the server; production deployments are unaffected.
An attacker with network reachability can send crafted requests directly to a development-mode instance and obtain arbitrary code execution, resulting in full compromise of confidentiality, integrity, and availability on the host without requiring credentials or user interaction.
The issue was resolved in release 3.3.2; the project published a security advisory and applied the corrective commit that eliminates the pre-authentication code path.
EPSS scores rose from a low baseline to a peak of 0.0194 before receding to the current value of 0.0091, indicating limited but observable post-disclosure interest that has since subsided.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-35701
Vulnerability details
Kottster is a self hosted Node.js admin panel. From versions 3.2.0 to before 3.3.2, Kottster contains a pre-authentication remote code execution (RCE) vulnerability when running in development mode. This affects development mode only, production deployments were never affected. This issue…
more
has been fixed in version 3.3.2.
- CWE(s)
Related Threats
No named actor attribution yet. ATT&CK technique mapping in progress for this CVE.
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Platform-independent apps typically execute inside a managed runtime or sandbox that restricts direct OS command execution, reducing the ability to exploit OS command injection.
The access control policy and procedures directly mandate and enforce proper access control mechanisms across the organization.
Device lock enforces restricted access until re-authentication, directly reducing unauthorized use of active sessions.
Supervision and review of access control activities directly detects and remediates improper access configurations or usages.
Explicitly identifying and documenting actions permitted without identification or authentication enforces proper access control boundaries by defining justified exceptions.
By automatically labeling outputs with security attributes, the control supports attribute-based enforcement and reduces exploitability of improper access control weaknesses.
Associating and retaining security attributes with data directly supports enforcement of access control decisions across storage, processing, and transmission.
Requiring prior authorization for each remote access type prevents improper access control over remote connections.