dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2025-11320

MEDIUM · 6.3 CVSS v3.1 Published 2025-10-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
A security vulnerability has been detected in zhuimengshaonian wisdom-education up to 1.0.4. Impacted is the function uploadFile of the file src/main/java/com/education/core/controller/UploadController.java. Such manipulation of the argument File leads to unrestricted upload. 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 · high confidence

The zhuimengshaonian wisdom-education platform up to version 1.0.4 contains an unrestricted file upload vulnerability in the uploadFile function of UploadController.java. An attacker can upload arbitrary files including executable content by manipulating the File argument, potentially leading to remote code execution if uploaded files are stored in a web-accessible location.

MitigationImplement strict file type validation using both MIME type checking and magic byte verification, rename uploaded files with random identifiers, store uploads outside the web root or in non-executable locations, and impose file size limits.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the zhuimengshaonian wisdom-education platform is installed
    Search for files or directories containing 'zhuimengshaonian' or 'wisdom-education' in the application root, or look for the application name in deployed WAR files, JAR files, or web application directories.
    Affected if The platform is present in the environment.
  2. Determine the installed version
    Look for version information in configuration files (such as version.properties, application.yml, pom.xml), build artifacts, or the application startup banner/logs. Compare the version number to 1.0.4.
    Affected if The installed version is 1.0.4 or lower.
  3. Locate the UploadController.java file
    Search the deployed source code or decompiled classes for UploadController.java, specifically the uploadFile function. This may be found in the application's source directory or decompiled from compiled classes.
    Affected if The vulnerable UploadController.java with uploadFile function exists in the deployment.
  4. Verify the file upload endpoint is accessible
    Check application routing/configuration to determine if the upload functionality is exposed via HTTP. Look for URL patterns related to file upload (such as /upload, /uploadFile, or similar endpoints) in the application's routing configuration.
    Affected if The upload endpoint is exposed and accessible via the web.
  5. Check upload storage location configuration
    Inspect application configuration to determine where uploaded files are stored. Look for upload path settings in configuration files or the upload handling code to see if files are saved within the web root (such as /uploads/, /static/, or /webapp/ directories).
    Affected if Uploaded files are stored in a web-accessible directory that allows execution.

A user is affected if the zhuimengshaonian wisdom-education platform version 1.0.4 or lower is deployed with the uploadFile function accessible and files stored in a web-accessible location.

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

Implement strict file type validation using both MIME type checking and magic byte verification, rename uploaded files with random identifiers, store uploads outside the web root or in non-executable locations, and impose file size limits.

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-11320 — 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-11320 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