dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-60803

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Antabot White-Jotter up to commit 9bcadc was discovered to contain an unauthenticated remote code execution (RCE) vulnerability via the component /api/aaa;/../register.

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 confidence

The Antabot White-Jotter application up to commit 9bcadc contains an unauthenticated remote code execution vulnerability. Attackers can exploit the /api/aaa;/../register endpoint by using path traversal sequences (;/../) to bypass access controls and achieve RCE without authentication.

MitigationApply immediate input validation and sanitization on all API endpoints, specifically blocking path traversal characters in request paths. Consider disabling or restricting the registration endpoint until properly secured with authentication.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Antabot White-Jotter application
    Locate the application installation directory or running service for the White-Jotter application in your environment
    Affected if The Antabot White-Jotter software is present
  2. Determine installed version or commit
    Inspect the source code repository, build configuration, or application metadata to find the current commit hash or version identifier
    Affected if The version is at commit 9bcadc or an earlier commit
  3. Verify registration endpoint exposure
    Attempt to access the /api/register endpoint via HTTP from an unauthenticated client to confirm if registration is publicly accessible
    Affected if The endpoint accepts unauthenticated requests
  4. Test path traversal bypass
    Send a request to /api/aaa;/../register using the semicolon path traversal sequence and verify if it bypasses any access controls
    Affected if The bypass sequence allows unauthenticated access to restricted functionality

The environment is affected if running Antabot White-Jotter at commit 9bcadc or earlier with the /api/aaa;/../register endpoint accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply immediate input validation and sanitization on all API endpoints, specifically blocking path traversal characters in request paths. Consider disabling or restricting the registration endpoint until properly secured with authentication.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-60803 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-60803 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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