gz-yami mall4j up to 4.0 Session Authentication A05_sys_menu_missing_perm.py sysType improper authorization

Summaryinfo

A vulnerability has been found in gz-yami mall4j up to 4.0 and classified as critical. Affected by this issue is some unknown functionality of the file A05_sys_menu_missing_perm.py of the component Session Authentication. Performing a manipulation of the argument sysType results in improper authorization. This vulnerability is known as CVE-2026-102364. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability was found in gz-yami mall4j up to 4.0. It has been classified as critical. This affects an unknown part of the file A05_sys_menu_missing_perm.py of the component Session Authentication. The manipulation of the argument sysType with an unknown input leads to a improper authorization vulnerability. CWE is classifying the issue as CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

mall4j through 4.0 fails to validate the sysType field in sa-token sessions, allowing storefront customers to authenticate as back-office users by reusing their session tokens. Attackers can register on the public storefront and use their customer session token to access admin endpoints lacking @PreAuthorize permission checks, including menu listings, file uploads, and configuration endpoints.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-102364 since 09/29/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/29/2026). MITRE ATT&CK project uses the attack technique T1548.002 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• gz-yami

Name

• mall4j

Version

• 4.0

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion