CVE-2025-13266
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 security vulnerability has been detected in wwwlike vlife up to 2.0.1. This issue affects the function create of the file vlife-base/src/main/java/cn/wwwlike/sys/api/SysFileApi.java of the component VLifeApi. Such manipulation of the argument fileName leads to path traversal. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used.
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 · moderate confidenceA path traversal vulnerability exists in wwwlike vlife up to version 2.0.1 in the SysFileApi.java component. The create function fails to properly sanitize the fileName parameter, allowing attackers to manipulate file paths using ../ sequences to write files outside the intended upload directory. This is a server-side vulnerability exploitable remotely.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
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 wwwlike vlife versionLocate the application deployment and check the version identifier (typically in manifest files, build metadata, or application properties). Compare the installed version to the affected range: any version up to and including 2.0.1 is vulnerable.Affected if The installed version is 2.0.1 or lower.
-
Locate SysFileApi.java componentSearch the application source code or deployed artifacts for the file SysFileApi.java. This component contains the vulnerable create function.Affected if SysFileApi.java exists in the deployment and contains a create function that accepts a fileName parameter.
-
Verify file upload endpoint is exposedIdentify and inspect the web service endpoint or API route that exposes the create function in SysFileApi.java. Check if it accepts HTTP requests (typically POST) with a fileName parameter.Affected if The create function endpoint is accessible over the network and accepts fileName input.
-
Check input sanitization on fileName parameterReview the source code of the create function in SysFileApi.java. Look for input validation logic that processes the fileName parameter before using it in file operations.Affected if The code lacks proper sanitization (such as basename() extraction) and allows ../ sequences to pass through the fileName parameter unchecked.
A system is affected if it runs wwwlike vlife version 2.0.1 or lower, has the SysFileApi.java component with an exposed create function, and does not sanitize the fileName parameter to block path traversal sequences.
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 on the fileName parameter using basename() to extract only the filename, combined with allowlist validation. Additionally, restrict the upload directory to a non-system location and enforce file type restrictions.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13266 — 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-13266 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