CVE-2026-9374
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 found in yangzongzhuan RuoYi-Vue up to 3.9.2. Impacted is the function FileUploadUtils.upload of the file /common/upload of the component Common Upload Endpoint. Performing a manipulation results in unrestricted upload. The attack is possible to be carried out remotely. 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 · moderate confidenceUnrestricted file upload vulnerability in the /common/upload endpoint of RuoYi-Vue up to version 3.9.2 allows remote attackers to upload arbitrary files without proper validation through the FileUploadUtils.upload function.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify RuoYi-Vue installationLocate the RuoYi-Vue application in your environment. Check for the presence of the fileupload-utils or common module JARs, or the project source code if available.Affected if RuoYi-Vue framework is deployed in the environment
-
Verify /common/upload endpoint exposureReview your web server or application routing configuration to determine if the /common/upload endpoint is accessible. Check Spring MVC or similar routing configurations for route definitions related to /common/upload.Affected if The /common/upload endpoint is exposed and accessible without additional authentication
-
Inspect FileUploadUtils.upload implementationLocate the FileUploadUtils.java or equivalent upload utility class in the codebase. Examine the upload method to verify whether file type validation exists and whether it uses an allowlist or denylist approach.Affected if FileUploadUtils.upload lacks proper file type validation or uses only a denylist approach without allowlist verification
-
Check uploaded file storage locationReview the configuration or code that defines where uploaded files are stored. Determine if uploaded files are placed in web-accessible directories (such as static, upload, or media folders served directly by the web server).Affected if Uploaded files are stored in directories accessible via direct URL (e.g., /static/, /uploads/, /media/)
Your environment is affected if RuoYi-Vue is deployed with the /common/upload endpoint accessible and FileUploadUtils.upload lacks strict allowlist-based file type validation, or if uploaded files are stored in web-accessible directories.
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 allowlist-based file type validation, validate file content (magic bytes), store uploads outside web root, and rename uploaded files to prevent direct execution.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9374 — 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-2026-9374 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