dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-13528

HIGH · 7.3 CVSS v3.1 Published 2026-06-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click 7 weeks old

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 was found in YunaiV/zhijiantianya ruoyi-vue-pro up to 2026.04-jdk8-SNAPSHOT. The impacted element is the function generateUploadPath of the file yudao-module-infra/src/main/java/cn/iocoder/yudao/module/infra/service/file/FileServiceImpl.java of the component AppFileController File Upload Endpoint. Performing a manipulation results in path traversal. Remote exploitation of the attack is possible. The exploit has been made public and could be used. The patch is named 4ae3f6b2c9883978837638c14e3d18419819eeb0. It is recommended to apply a patch to fix this issue. This product is published by multiple vendors.

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 generateUploadPath function within FileServiceImpl.java of the ruoyi-vue-pro application. The file upload endpoint (AppFileController) fails to properly sanitize file path inputs, allowing attackers to use '../' sequences in filenames to write files outside the intended upload directory. This can lead to arbitrary file write access on the server.

MitigationApply the provided patch (commit 4ae3f6b) which adds proper path sanitization to the generateUploadPath function. Ensure all user-supplied filename/path input is validated, normalized, and restricted to the intended upload directory using canonical path comparisons.

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
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Locate the FileServiceImpl.java file
    Search the application source code or decompiled classes for FileServiceImpl.java in the file service implementation path
    Affected if The file exists in the ruoyi-vue-pro application codebase and contains a generateUploadPath function without canonical path validation
  2. Inspect the generateUploadPath function
    Examine the generateUploadPath function in FileServiceImpl.java for path traversal protection - look for code that validates or normalizes file paths (e.g., canonical path comparison, path sanitization logic)
    Affected if The function lacks proper path sanitization and allows '../' sequences to pass through without validation
  3. Check AppFileController file upload endpoint
    Locate AppFileController.java and verify it uses generateUploadPath for file uploads - confirm the endpoint accepts user-supplied filenames without validation
    Affected if The file upload endpoint passes user-provided filenames directly to generateUploadPath without sanitization
  4. Verify patch commit 4ae3f6b
    Check the git history or source control for commit 4ae3f6b - verify if the patch adding path sanitization has been applied to the generateUploadPath function
    Affected if Commit 4ae3f6b is not present in the codebase or the generateUploadPath function does not contain the canonical path validation added by the patch
  5. Test path traversal in upload functionality
    If the application is running, attempt to upload a file with a filename containing '../' sequences (e.g., '../test.txt') through the file upload endpoint
    Affected if The application allows writing files outside the intended upload directory using path traversal sequences

You are affected if the ruoyi-vue-pro application uses a generateUploadPath function in FileServiceImpl.java that lacks proper path sanitization and the patch from commit 4ae3f6b has not been applied.

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

Apply the provided patch (commit 4ae3f6b) which adds proper path sanitization to the generateUploadPath function. Ensure all user-supplied filename/path input is validated, normalized, and restricted to the intended upload directory using canonical path comparisons.

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-2026-13528 — 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-2026-13528 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