CVE Vulnerabilities

CVE-2026-3187

Improper Access Control

Published: Feb 25, 2026 | Modified: Feb 26, 2026
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu
root.io logo minimus.io logo echo.ai logo

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.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

NameVendorStart VersionEnd Version
Sz-boot-parentSzadmin*0.9.0 (including)
Sz-boot-parentSzadmin1.0.0-beta (including)1.0.0-beta (including)
Sz-boot-parentSzadmin1.0.1-beta (including)1.0.1-beta (including)
Sz-boot-parentSzadmin1.0.2-beta (including)1.0.2-beta (including)
Sz-boot-parentSzadmin1.1.0-beta (including)1.1.0-beta (including)
Sz-boot-parentSzadmin1.2.0-beta (including)1.2.0-beta (including)
Sz-boot-parentSzadmin1.2.1-beta (including)1.2.1-beta (including)
Sz-boot-parentSzadmin1.2.2-beta (including)1.2.2-beta (including)
Sz-boot-parentSzadmin1.2.3-beta (including)1.2.3-beta (including)
Sz-boot-parentSzadmin1.2.4-beta (including)1.2.4-beta (including)
Sz-boot-parentSzadmin1.2.5-beta (including)1.2.5-beta (including)
Sz-boot-parentSzadmin1.2.6-beta (including)1.2.6-beta (including)
Sz-boot-parentSzadmin1.3.0-beta (including)1.3.0-beta (including)
Sz-boot-parentSzadmin1.3.1-beta (including)1.3.1-beta (including)
Sz-boot-parentSzadmin1.3.2-beta (including)1.3.2-beta (including)

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References