VulnerabilityPublished 4 Jan 2026Updated 23 Feb 2026

CVE-2026-0574: yeqifu warehouse · Improper Authorization

Affects yeqifu warehouseSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
yeqifuwarehouse	Affected =aaf29962ba407d22d991781de28796ee7b4670e4	Fixed in–

AI-suggested

To mitigate CVE-2026-0574, organizations should immediately audit and restrict access to the saveUserRole functionality, ensuring only fully authorized administrators can invoke role changes. Implement strict role-based access control (RBAC) policies and enforce multi-factor authentication (MFA) for administrative accounts to reduce risk of compromised credentials. Review application logs for unusual or unauthorized role modification attempts. Since the product uses a rolling release model, coordinate closely with yeqifu vendor or community to obtain the latest patches or commits that address this vulnerability. If patches are not yet available, consider implementing temporary compensating controls such as network segmentation, IP whitelisting, or web application firewalls (WAF) to restrict access to the vulnerable endpoints. Conduct thorough code reviews and penetration testing focused on authorization logic to identify and remediate similar flaws. Educate administrators about the risk and signs of exploitation. Maintain an incident response plan to quickly contain and remediate any detected exploitation attempts.

Description

A weakness has been identified in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. This affects the function saveUserRole of the file warehouse\src\main\java\com\yeqifu\sys\controller\UserController.java of the component Request Handler. This manipulation causes improper authorization. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified.

Impact

The improper authorization vulnerability in yeqifu warehouse can have significant impacts on organizations relying on this software for warehouse or supply chain management. Unauthorized modification of user roles can lead to privilege escalation, allowing attackers to gain administrative or otherwise elevated access. This can result in unauthorized data access, manipulation of inventory or order processing, disruption of business operations, and potential data integrity issues. Since the attack can be performed remotely without user interaction or elevated privileges, the attack surface is broad. The public availability of exploit code increases the likelihood of exploitation attempts. Organizations with sensitive or critical supply chain operations could face operational downtime, financial losses, and reputational damage. The rolling release nature of the product complicates timely patching, potentially prolonging exposure. While no widespread exploitation is reported yet, the medium severity rating indicates a tangible risk that should be addressed promptly.

Summary

CVE-2026-0574 identifies an improper authorization vulnerability in the yeqifu warehouse software, specifically within the saveUserRole function of the UserController.java component. This flaw allows an attacker with limited privileges to remotely invoke the saveUserRole function and manipulate user roles without proper authorization checks. The vulnerability arises from insufficient validation of the requester's permissions before allowing role changes, which can lead to privilege escalation or unauthorized access modifications. The product follows a rolling release strategy, meaning updates are continuously delivered without discrete versioning, complicating patch management and vulnerability tracking. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no authentication required (AT:N), no user interaction (UI:N), and limited impact on confidentiality, integrity, and availability (VC:L, VI:L, VA:L). Although no known exploits in the wild have been reported, the public availability of exploit code increases the risk of exploitation. The vulnerability affects all versions up to the commit aaf29962ba407d22d991781de28796ee7b4670e4, but exact versioning is unclear due to the rolling release model. This vulnerability is critical in environments where role-based access control is essential for security, as unauthorized role changes can lead to privilege escalation and potential data breaches or operational disruption.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 23:12 UTC

Technical details

References

Community reviews

Related threats