dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-34040

CRITICAL · 10.0 CVSS v4.0 Published 2025-06-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
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
An arbitrary file upload vulnerability exists in the Zhiyuan OA platform via the wpsAssistServlet interface. The realFileType and fileId parameters are improperly validated during multipart file uploads, allowing unauthenticated attackers to upload crafted JSP files outside of intended directories using path traversal. Successful exploitation enables remote code execution as the uploaded file can be accessed and executed through the web server. Exploitation evidence was observed by the Shadowserver Foundation on 2025-02-01 UTC.

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

Arbitrary file upload vulnerability in Zhiyuan OA's wpsAssistServlet allows unauthenticated attackers to bypass validation on realFileType and fileId parameters during multipart uploads. Path traversal enables uploading malicious JSP files to arbitrary directories outside the intended upload path, leading to remote code execution when the web server serves and executes the uploaded JSP files.

MitigationDisable or restrict the wpsAssistServlet interface immediately; implement strict allowlist validation on file type and fileId/path parameters to prevent path traversal, and store uploads outside the web root with no executable permissions.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 Zhiyuan OA installation
    Search for Zhiyuan OA installation directories (commonly under /oa, /Zhiyuan, or similar webapp paths) or check running processes for 'Zhiyuan' or 'OA' related Java services
    Affected if Zhiyuan OA software is present on the system
  2. Locate wpsAssistServlet
    Examine the web application's web.xml deployment descriptor or check deployed WAR file contents for 'wpsAssistServlet' servlet mapping
    Affected if wpsAssistServlet is mapped and deployed in the web application
  3. Check wpsAssistServlet accessibility
    Verify if the servlet is exposed via HTTP/HTTPS (typically at /wpsAssistServlet or similar path under the OA context root) using web server access logs or by attempting a HEAD request to the endpoint
    Affected if The servlet is web-accessible and accepts requests
  4. Identify installed version
    Check for version information in Zhiyuan OA installation directories, About pages within the OA application, or version files in the deployment (such as version.properties, about.html, or manifest.mf)
    Affected if The installed version matches any known affected version range (compare your version to the affected releases)
  5. Inspect upload directory configuration
    Examine the web application configuration and file system for upload directories (often under webapp root or configurable upload folders); check if uploads are stored within the web root
    Affected if Uploads are stored in web-accessible directories where JSP files could be executed

Your environment is affected if Zhiyuan OA with an accessible wpsAssistServlet is installed and the upload functionality is enabled, allowing unauthenticated file uploads to web-accessible directories.

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

Disable or restrict the wpsAssistServlet interface immediately; implement strict allowlist validation on file type and fileId/path parameters to prevent path traversal, and store uploads outside the web root with no executable permissions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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