dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-10213

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
A security flaw has been discovered in AstrBotDevs AstrBot 4.23.6. This vulnerability affects unknown code of the file /api/skills/delete of the component API Endpoint. Performing a manipulation of the argument Name results in path traversal. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.

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

Path traversal vulnerability in AstrBot 4.23.6 affecting the /api/skills/delete API endpoint. By manipulating the 'Name' argument, an attacker can potentially access or delete files outside the intended directory, leading to unauthorized file system access. The attack is remotely exploitable and a public exploit exists.

MitigationImplement strict input validation and sanitization for the Name parameter to restrict path traversal sequences (../). Alternatively, restrict network access to the API endpoint until vendor patch is available. Consider deploying a WAF as a temporary measure.

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

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

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 installed AstrBot version
    Check the running AstrBot version by inspecting the application startup logs, configuration files, or using the application's version endpoint/command (e.g., looking in package.json, version file, or running 'astrbot --version' if available)
    Affected if The installed version is 4.23.6 or falls within the affected range around 4.23.6
  2. Confirm /api/skills/delete endpoint exists
    Review the AstrBot source code, API route definitions, or OpenAPI/Swagger documentation to verify the /api/skills/delete endpoint is implemented in the codebase
    Affected if The endpoint exists in the codebase, indicating the vulnerable code is present
  3. Check if skills feature is enabled
    Inspect the AstrBot configuration (e.g., config.json, settings.yaml, or environment variables) to determine whether the skills module or plugin is loaded and active
    Affected if The skills functionality is enabled and accessible to users
  4. Identify skills directory location
    Locate the configured skills directory by reviewing configuration files for the 'skills_path', 'skills_dir', or similar setting, or by searching for the default 'skills' directory in the application root
    Affected if A skills directory is configured and the application has file system access to it
  5. Verify API is network accessible
    Determine if the AstrBot API server is exposed to the network (check bind address configuration, firewall rules, or reverse proxy settings) and whether authentication is required for the /api/skills/delete endpoint
    Affected if The API endpoint is accessible without proper authentication or from untrusted networks

A user is affected if running AstrBot version 4.23.6 (or a version containing this vulnerability) with the skills module enabled and the /api/skills/delete API endpoint accessible to attackers who can supply directory traversal sequences in the Name parameter.

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

Implement strict input validation and sanitization for the Name parameter to restrict path traversal sequences (../). Alternatively, restrict network access to the API endpoint until vendor patch is available. Consider deploying a WAF as a temporary measure.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-10213 — 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-2026-10213 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