CVE-2025-50857
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 · uneditedZenTaoPMS v18.11 through v21.6.beta is vulnerable to Directory Traversal in /module/ai/control.php. This allows attackers to execute arbitrary code via a crafted file upload
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 confidenceZenTaoPMS versions 18.11 through 21.6.beta contain a directory traversal vulnerability in /module/ai/control.php. Attackers can exploit improper input validation during file upload operations to traverse directory paths and write arbitrary files, potentially achieving remote code execution on the server.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ZenTaoPMS versionAccess the ZenTao administration panel and navigate to the About or System Information page to view the current version number. Alternatively, check the version file in the installation directory if accessible.Affected if The installed version is 18.11, 18.12, 19.x, 20.x, 21.0, 21.1, 21.2, 21.3, 21.4, 21.5, or 21.6.beta (any version from 18.11 through 21.6.beta inclusive).
-
Verify presence of vulnerable ai moduleCheck if the /module/ai/ directory exists in the ZenTao installation root. Look for the control.php file within that directory.Affected if The file /module/ai/control.php exists on the server, indicating the ai module is installed.
-
Confirm ai module is enabledLog into the ZenTao admin panel and navigate to the module management or extension settings. Verify whether the ai module is listed as active or enabled.Affected if The ai module is enabled and accessible to users in the system.
-
Check file upload capability in ai moduleExamine the /module/ai/control.php file for functions related to file uploads, particularly any upload handling logic that processes user-provided filenames or paths.Affected if The ai module contains file upload functionality that accepts user-supplied paths or filenames.
You are affected if your ZenTaoPMS version falls between 18.11 and 21.6.beta inclusive AND the ai module with file upload capability is enabled on your server.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to a patched version beyond v21.6.beta. If immediate patching is not possible, implement web application firewall rules to block path traversal patterns (../, ..\) in upload requests and temporarily disable the affected ai module until the fix is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-50857 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-50857 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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