Skip to main content
CVE-2025-60803VulnerabilityPublished

CVE-2025-60803: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Oct 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

AI-suggested

1. Immediately restrict network access to the /api/aaa;/../register endpoint using firewalls, access control lists, or web application firewalls (WAFs) to limit exposure to trusted IPs only. 2. Monitor network traffic and logs for unusual requests targeting the vulnerable endpoint, especially those containing suspicious command injection patterns. 3. Employ intrusion detection/prevention systems (IDS/IPS) with updated signatures to detect exploitation attempts. 4. Isolate affected systems from critical network segments until patches or updates are available. 5. Engage with Antabot White-Jotter vendors or development teams to obtain patches or mitigations as soon as they are released. 6. Conduct thorough security audits and penetration testing focused on command injection vulnerabilities in similar components. 7. Implement application-layer input validation and sanitization where possible to reduce injection risks. 8. Prepare incident response plans specific to RCE scenarios to enable rapid containment and recovery. 9. Educate IT and security teams about this vulnerability to ensure awareness and readiness. 10. Consider deploying endpoint detection and response (EDR) tools to identify post-exploitation activities.

Description

Antabot White-Jotter up to commit 9bcadc was discovered to contain an unauthenticated remote code execution (RCE) vulnerability via the component /api/aaa;/../register.

References

Community reviews

Loading reviews…