CVE-2025-11139
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 · uneditedA vulnerability was determined in Bjskzy Zhiyou ERP up to 11.0. Affected is the function uploadStudioFile of the component com.artery.form.services.FormStudioUpdater. This manipulation of the argument filepath causes path traversal. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. 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 · high confidenceA path traversal vulnerability exists in Bjskzy Zhiyou ERP (versions up to 11.0) within the uploadStudioFile function of the FormStudioUpdater component. The filepath argument is not properly validated, allowing attackers to manipulate file paths using '../' sequences to write files outside the intended directory. Remote attackers can exploit this without authentication due to the critical CVSS score of 9.8.
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<= 11.0CVSS 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.
-
Confirm Zhiyou ERP installationIdentify if Zhiyou ERP (Zhiyou Group Zhiyou Erp) is installed in your environment by searching for installation directories, service processes, or web application endpoints associated with this product.Affected if The product is present in the environment.
-
Check installed versionLocate and inspect version information for the Zhiyou ERP installation. Common locations include: version files in the application root, about/help pages within the web interface, or configuration files that store version metadata. Compare your installed version against the affected range of <= 11.0.Affected if The installed version is 11.0 or any version number lower than 11.0.
-
Identify FormStudioUpdater componentSearch the application installation directory for files or modules named FormStudioUpdater, FormStudio, or related components that handle file upload functionality.Affected if The FormStudioUpdater component exists in the installation.
-
Verify uploadStudioFile function accessibilityExamine the application's routing, URL patterns, or API endpoints to determine if the uploadStudioFile function is exposed and accessible. This may involve reviewing application configuration, routing tables, or attempting to access known upload endpoints.Affected if The uploadStudioFile function is accessible via HTTP/HTTPS without authentication.
You are affected if Zhiyou ERP is installed with version 11.0 or lower and the FormStudioUpdater component with its uploadStudioFile function is present and accessible.
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 dataImplement strict input validation and sanitization on the filepath parameter, using allowlists and canonicalization to ensure only permitted paths are accepted. Additionally, enforce proper access controls on the upload functionality and consider deploying a WAF as a defense-in-depth measure.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11139 — 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-11139 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