CVE-2025-52395: Roadcute API · Improper Authentication
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 13:47 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
Organizations should immediately audit their use of Roadcute API v1 and identify all instances where the password reset API endpoint is exposed. Since no official patches are currently available, it is essential to implement compensating controls such as restricting access to the password reset endpoint via network-level controls (e.g., IP whitelisting, VPN access), enforcing multi-factor authentication (MFA) on password reset workflows, and monitoring API logs for suspicious activity indicative of exploitation attempts. Additionally, organizations should consider deploying Web Application Firewalls (WAFs) with custom rules to detect and block anomalous requests targeting the password reset endpoint. Security teams must prepare incident response plans specific to this vulnerability and maintain heightened vigilance until a vendor patch is released. Regularly updating and hardening authentication mechanisms and conducting penetration testing focused on API security will further reduce risk exposure.
Description
An issue in Roadcute API v.1 allows a remote attacker to execute arbitrary code via the application exposing a password reset API endpoint that fails to validate the identity of the requester properly