VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2026-2079: 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 22% 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 7 Feb 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

Implement strict access control checks in the addMenu, updateMenu, and deleteMenu functions to ensure only authorized users can perform these operations.
Conduct a thorough code audit of the MenuController.java and related components to identify and remediate any other authorization weaknesses.
Employ runtime application self-protection (RASP) or web application firewalls (WAFs) with custom rules to detect and block unauthorized menu management requests.
Monitor logs for unusual activity related to menu operations, including unexpected additions, updates, or deletions.
Restrict network access to the yeqifu warehouse management interfaces to trusted IP ranges or VPNs to reduce exposure.
Engage with the yeqifu project maintainers to obtain patches or updates addressing this vulnerability.
If possible, implement multi-factor authentication and role-based access control (RBAC) to limit the impact of compromised credentials.
Prepare incident response plans to quickly address potential exploitation attempts.
Consider temporary disabling of menu management functions if feasible until a patch is available.

Description

A flaw has been found in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. This vulnerability affects the function addMenu/updateMenu/deleteMenu of the file dataset\repos\warehouse\src\main\java\com\yeqifu\sys\controller\MenuController.java of the component Menu Management. Executing a manipulation can lead to improper authorization. The attack may be launched remotely. The exploit has been published and may be used. This product operates on a rolling release basis, ensuring continuous delivery. Consequently, there are no version details for either affected or updated releases. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The improper authorization vulnerability in yeqifu warehouse can lead to unauthorized modification or deletion of menu configurations, impacting the integrity and availability of the affected system's menu management functionality. For organizations relying on yeqifu warehouse for critical operations, this could disrupt normal workflows, cause denial of service in menu-dependent processes, or facilitate further attacks if attackers leverage altered menus to escalate privileges or inject malicious configurations. Since exploitation requires no authentication or user interaction and can be performed remotely, the attack surface is broad. However, the overall impact on confidentiality is low, as the vulnerability does not directly expose sensitive data. The medium severity rating reflects a moderate risk that could escalate if combined with other vulnerabilities or misconfigurations. Organizations worldwide using this software, especially in sectors where menu management controls access to critical functions, may face operational disruptions and increased risk of compromise.

Summary

CVE-2026-2079 identifies an improper authorization vulnerability in the yeqifu warehouse software, specifically within the Menu Management component's addMenu, updateMenu, and deleteMenu functions located in the MenuController.java source file. This flaw allows an unauthenticated remote attacker to perform unauthorized operations on menu data, bypassing intended access controls. The vulnerability arises from insufficient authorization checks in these functions, enabling manipulation of menu entries without proper permissions. The product follows a rolling release development model, which complicates version tracking; the affected code is identified by a specific commit hash (aaf29962ba407d22d991781de28796ee7b4670e4). The vulnerability has a CVSS 4.0 score of 5.3, reflecting medium severity due to its ease of exploitation (no authentication or user interaction required) but limited impact scope (low confidentiality, integrity, and availability impact). No known active exploitation in the wild has been documented, but a public exploit exists, increasing the risk of future attacks. The vulnerability primarily threatens the integrity and availability of menu management functions, potentially allowing attackers to alter or delete menu configurations, which could disrupt application workflows or lead to further privilege escalation if combined with other vulnerabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:24 UTC

Technical details

References

Community reviews

Related threats