dbcve.org
OpenagentsApplication · Xlang

CVE-2025-6282

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-19
Fix available
A fix is available. Upgrade to after 2024-11-18 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A vulnerability was found in xlang-ai OpenAgents up to ff2e46440699af1324eb25655b622c4a131265bb and classified as critical. Affected by this issue is the function create_upload_file of the file backend/api/file.py. The manipulation leads to path traversal. The exploit has been disclosed to the public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The reported GitHub issue was closed automatically with the label "not planned" by a bot.

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 · high confidence

A path traversal vulnerability exists in the create_upload_file function of backend/api/file.py in xlang-ai OpenAgents. The function fails to properly validate or sanitize file paths during upload, allowing attackers to write files to arbitrary locations on the server filesystem. This critical flaw (CVSS 9.8) could enable remote code execution or complete system compromise.

MitigationSince the vendor has closed the issue as 'not planned', organizations must implement custom mitigation: add strict path validation to reject '../' sequences and other path traversal attempts in filenames, restrict uploaded files to a whitelisted secure directory, and consider implementing file content validation. Deploy behind a WAF as an interim control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpenagentsApplication
Affected:<= 2024-11-18

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 OpenAgents installation and version
    Locate the xlang-ai OpenAgents installation directory and check the version metadata (e.g., pyproject.toml, setup.py, version file, or git tags). Compare against the affected version: <= 2024-11-18
    Affected if OpenAgents is installed and the version is dated 2024-11-18 or earlier
  2. Verify vulnerable file exists
    Check if the file backend/api/file.py exists in the installation directory. This file contains the create_upload_file function with the path traversal flaw
    Affected if The file backend/api/file.py exists in the OpenAgents installation
  3. Confirm upload endpoint is exposed
    Inspect the application routing configuration (e.g., main.py, app.py, or API router files) to determine if the file upload endpoint using create_upload_file is registered and accessible. Look for routes that reference the upload function or file.py
    Affected if The file upload endpoint is registered and accessible via the API router
  4. Check if uploads directory is configured
    Examine the application configuration (config files, environment variables, or settings.py) to see if an upload directory is defined and writable by the application. The vulnerability requires a writable upload path to be exploitable
    Affected if A writable upload directory is configured in the application settings
  5. Inspect the create_upload_file function
    Open backend/api/file.py and examine the create_upload_file function implementation. Look for path validation logic that checks for '../' sequences, absolute paths, or other traversal patterns in the filename parameter
    Affected if The create_upload_file function lacks proper path sanitization (no validation of '../' or absolute path inputs)

You are affected if OpenAgents version <= 2024-11-18 is installed, the backend/api/file.py exists, the upload endpoint is exposed, and the create_upload_file function lacks path traversal validation.

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
Upgrade available Upgrade to a release after 2024-11-18
Interim mitigation

Since the vendor has closed the issue as 'not planned', organizations must implement custom mitigation: add strict path validation to reject '../' sequences and other path traversal attempts in filenames, restrict uploaded files to a whitelisted secure directory, and consider implementing file content validation. Deploy behind a WAF as an interim control.

Fix this in Openagents Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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