dbcve.org
Sz Boot ParentApplication · Szadmin

CVE-2026-3187

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-25
Fix available
A fix is available. Upgrade to after 0.9.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 identified in feiyuchuixue sz-boot-parent up to 1.3.2-beta. Affected by this issue is some unknown functionality of the file /api/admin/sys-file/upload of the component API Endpoint. Such manipulation leads to unrestricted upload. The attack may be launched remotely. The exploit is publicly available and might be used. Upgrading to version 1.3.3-beta can resolve this issue. The name of the patch is aefaabfd7527188bfba3c8c9eee17c316d094802. Upgrading the affected component is recommended. The project was informed beforehand and acted very professional: "We have introduced a whitelist restriction on the /api/admin/sys-file/upload endpoint via the oss.allowedExts and oss.allowedMimeTypes configuration options, allowing the specification of permitted file extensions and MIME types for uploads."

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

Unrestricted file upload vulnerability in the /api/admin/sys-file/upload API endpoint of sz-boot-parent up to version 1.3.2-beta allows remote attackers to upload arbitrary files without validation of file type or content.

MitigationUpgrade to version 1.3.3-beta which implements whitelist restrictions via oss.allowedExts and oss.allowedMimeTypes configuration options to restrict allowed file extensions and MIME types.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sz Boot ParentApplication
Affected:<= 0.9.0= 1.0.0= 1.0.1= 1.0.2= 1.1.0= 1.2.0= 1.2.1= 1.2.2= 1.2.3= 1.2.4= 1.2.5= 1.2.6

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 sz-boot-parent version
    Locate the project dependency file (pom.xml, package.json, build.gradle, or similar) and find the sz-boot-parent version entry. Also check the main application properties or build files for the framework version.
    Affected if The installed version is <= 0.9.0, 1.0.0, 1.0.1, 1.0.2, 1.1.0, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, or 1.2.6 (any version up to and including 1.3.2-beta). Versions 1.3.3-beta and later are not affected.
  2. Verify the upload endpoint exists
    Check if the application exposes the /api/admin/sys-file/upload API endpoint. This is typically defined in the application's routing or controller configuration files.
    Affected if The endpoint /api/admin/sys-file/upload is present and accessible in the running application.
  3. Check for whitelist configuration
    Inspect the application configuration files (application.yml, application.properties, or similar) for oss.allowedExts and oss.allowedMimeTypes settings. These are the whitelist configuration options that were added in the patched version.
    Affected if No oss.allowedExts or oss.allowedMimeTypes configuration is defined, meaning the unrestricted file upload vulnerability is present.

If the sz-boot-parent version is 1.3.2-beta or earlier and no whitelist configuration (oss.allowedExts, oss.allowedMimeTypes) is present, the environment is affected by this unrestricted file upload vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 0.9.0
Vendor patch github.com →
Interim mitigation

Upgrade to version 1.3.3-beta which implements whitelist restrictions via oss.allowedExts and oss.allowedMimeTypes configuration options to restrict allowed file extensions and MIME types.

Recommended fix High confidence

1.3.3-beta

  1. 1. Locate the sz-boot-parent dependency in your project's build configuration file (pom.xml or build.gradle)
  2. 2. Update the sz-boot-parent version from your current version to 1.3.3-beta
  3. 3. Rebuild and redeploy the application
  4. 4. Verify the /api/admin/sys-file/upload endpoint now enforces file type restrictions
  5. 5. Optionally configure allowed extensions via oss.allowedExts and allowed MIME types via oss.allowedMimeTypes in your application configuration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sz Boot Parent Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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