dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-5029

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-21
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 vulnerability has been found in Kingdee Cloud Galaxy Private Cloud BBC System up to 9.0 Patch April 2025 and classified as critical. Affected by this vulnerability is the function BaseServiceFactory.getFileUploadService.deleteFileAction of the file fileUpload/deleteFileAction.jhtml of the component File Handler. The manipulation of the argument filePath leads to path traversal. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. It is recommended to apply a patch to fix this issue.

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 deleteFileAction function of Kingdee Cloud Galaxy Private Cloud BBC System (versions up to 9.0 Patch April 2025). The filePath parameter is not properly validated, allowing attackers to manipulate it with sequences like ../../ to delete arbitrary files on the server filesystem remotely.

MitigationImplement strict input validation on the filePath parameter to restrict deletions to an approved directory allowlist, apply the vendor patch if available, and consider disabling the delete functionality until a proper fix is deployed.

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 Kingdee Cloud Galaxy Private Cloud BBC System installation
    Locate the application by checking web server logs, installed programs, or common web application directories for Kingdee components. Look for the 'bbc' or 'Kingdee' directory structure in the web root.
    Affected if The Kingdee Cloud Galaxy Private Cloud BBC System is present on the server
  2. Determine the installed version
    Access the system's about page, administration panel, or check version files in the installation directory. Look for a version string such as '9.0' with a patch date.
    Affected if The installed version is 9.0 or any version up to and including the April 2025 patch release
  3. Verify deleteFileAction endpoint accessibility
    Check if the web application's deleteFileAction function is exposed. This is typically found in BBC-specific modules handling file operations. Review the application's URL routing or exposed API endpoints.
    Affected if The deleteFileAction function is accessible via the web interface or API without administrative authentication barriers
  4. Inspect filePath parameter validation
    Examine the deleteFileAction function code or configuration to verify whether the filePath parameter accepts path traversal sequences. Test by attempting a request with '../' in the filePath parameter to observe if the application rejects or sanitizes it.
    Affected if The filePath parameter accepts '../' sequences without sanitization or restriction to an allowed directory allowlist

A user is affected if Kingdee Cloud Galaxy Private Cloud BBC System version 9.0 or below (up to the April 2025 patch) is installed AND the deleteFileAction function is accessible without proper path traversal validation on the filePath 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 on the filePath parameter to restrict deletions to an approved directory allowlist, apply the vendor patch if available, and consider disabling the delete functionality until a proper fix is deployed.

Have this fixed 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 help mitigating

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-5029 — 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-5029 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