CVE-2026-2105VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2026-2105: yeqifu warehouse · Improper Authorization

Affects yeqifu warehouseSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 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 24% 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: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

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 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

1. Implement strict access control policies restricting who can access department management functions, ensuring only trusted and necessary users have such privileges. 2. Employ network segmentation and firewall rules to limit access to the yeqifu warehouse application, especially restricting access to the DeptController endpoints. 3. Monitor logs and audit trails for unusual activity related to department creation, updates, or deletions to detect potential exploitation attempts early. 4. Use Web Application Firewalls (WAFs) to detect and block suspicious requests targeting the vulnerable functions. 5. Engage in proactive vulnerability scanning and penetration testing focused on authorization controls within the application. 6. Contact the vendor or maintainers for updates and patches, and plan for rapid deployment once available. 7. Consider temporary compensating controls such as disabling or restricting the affected functions if feasible until a patch is released. 8. Educate internal users about the risk and encourage reporting of suspicious behavior related to department management.

Description

A flaw has been found in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. The affected element is the function addDept/updateDept/deleteDept of the file dataset\repos\warehouse\src\main\java\com\yeqifu\sys\controller\DeptController.java of the component Department Management. Executing a manipulation can lead to improper authorization. It is possible to launch the attack remotely. The exploit has been published and may be used. This product takes the approach of rolling releases to provide continious delivery. Therefore, version details for affected and updated releases are not available. 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 could allow attackers with low-level privileges to manipulate department data without proper authorization. This can lead to unauthorized creation, modification, or deletion of department records, potentially disrupting organizational workflows, causing data integrity issues, and leaking sensitive internal structure information. While the impact on confidentiality and availability is limited, integrity violations could affect business processes and decision-making. The remote exploitability and published exploit code increase the risk of targeted attacks, especially in environments where yeqifu warehouse is used for critical departmental management. Organizations may face operational disruptions, compliance risks, and reputational damage if exploited. The lack of vendor response and patch availability prolongs exposure, necessitating immediate mitigation efforts.

Summary

CVE-2026-2105 is an improper authorization vulnerability identified in the yeqifu warehouse software, specifically within the Department Management component's addDept, updateDept, and deleteDept functions in DeptController.java. This flaw allows an attacker to perform unauthorized operations on department data by bypassing intended access controls. The vulnerability is remotely exploitable and requires low privileges (PR:L), meaning the attacker must have some authenticated access but no elevated privileges. No user interaction is needed, and the attack vector is network-based (AV:N). The vulnerability impacts confidentiality, integrity, and availability at a low level, as unauthorized modifications to department data could disrupt organizational operations or leak sensitive information. The software's rolling release approach means affected and fixed versions are not clearly delineated, and the vendor has not yet issued a patch or official response. An exploit has been published, increasing the risk of exploitation despite no current reports of active attacks. The CVSS 4.0 score of 5.3 reflects a medium severity, balancing ease of exploitation with limited scope and impact. Organizations relying on yeqifu warehouse should be aware of this vulnerability and implement compensating controls until a patch is available.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats