dbcve.org
Improper Access ControlWeakness · CWE-284

CVE-2026-2665

MEDIUM · 6.3 CVSS v3.1 Published 2026-02-18
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 vulnerability was detected in huanzi-qch base-admin up to 57a8126bb3353a004f3c7722089e3b926ea83596. Impacted is the function Upload of the file SysFileController.java of the component JSP Parser. Performing a manipulation of the argument File results in unrestricted upload. The attack can be initiated remotely. The exploit is now public and may be used. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The project was informed of the problem early through an issue report but has not responded yet.

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 confidence

Unrestricted file upload vulnerability in the Upload function of SysFileController.java in huanzi-qch base-admin. The JSP Parser component fails to properly validate uploaded files, allowing remote attackers to upload malicious files (potentially JSP webshells) without restrictions. The exploit is publicly available and can be initiated remotely.

MitigationImplement strict server-side file validation including whitelist of allowed extensions, magic byte verification, storing uploads outside webroot, and disabling script execution permissions on upload directories. Consider using a dedicated file upload library with built-in security controls.

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. Identify if huanzi-qch base-admin is deployed
    Search for files named SysFileController.java or look for application signatures indicating huanzi-qch base-admin. Check web application directories for the presence of this controller class.
    Affected if The application is huanzi-qch base-admin and contains SysFileController.java with an Upload function
  2. Determine the installed version of base-admin
    Check the project's pom.xml, build.gradle, or WAR file manifest for the version number of huanzi-qch base-admin. Compare against any known affected version ranges.
    Affected if The installed version falls within the affected range (if any range is known)
  3. Verify if the file upload endpoint is exposed
    Check web.xml or application routing configuration to confirm the Upload function in SysFileController is publicly accessible. Look for routes like /file/upload or similar patterns.
    Affected if The upload endpoint is accessible without authentication or with weak authentication
  4. Inspect file upload validation logic
    Examine SysFileController.java or the associated upload service to check if file extension validation, content-type validation, or magic byte verification is implemented.
    Affected if No file type validation, extension whitelist, or content validation is performed before saving uploaded files
  5. Check upload directory configuration
    Review application configuration to determine if uploaded files are stored inside the webroot or in a location where they can be executed as scripts (JSP).
    Affected if Uploaded files are stored within the webroot and script execution is not disabled on that directory

You are affected if huanzi-qch base-admin is running with an exposed Upload function in SysFileController that lacks proper file validation and stores files in an executable 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 server-side file validation including whitelist of allowed extensions, magic byte verification, storing uploads outside webroot, and disabling script execution permissions on upload directories. Consider using a dedicated file upload library with built-in security controls.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2665 — 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-2665 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