VulnerabilityPublished 7 Feb 2026Updated 23 Feb 2026

CVE-2026-2107: 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 30% 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

Organizations should immediately audit and restrict access to the yeqifu warehouse Log Info Handler functions, ensuring that only trusted administrators have permissions to invoke loadAllLoginfo, deleteLoginfo, and batchDeleteLoginfo. Implement network-level access controls to limit exposure of the affected service to trusted IP ranges. Employ application-layer firewalls or WAFs to detect and block unauthorized API calls targeting these functions. Monitor logs for unusual access patterns or deletions indicative of exploitation attempts. Engage with the vendor for updates and track any forthcoming patches. If feasible, review and harden source code authorization logic to enforce strict privilege checks. Regularly back up log data to immutable storage to prevent loss from unauthorized deletions.

Description

A vulnerability was found in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. This affects the function loadAllLoginfo/deleteLoginfo/batchDeleteLoginfo of the file dataset\repos\warehouse\src\main\java\com\yeqifu\sys\controller\LoginfoController.java of the component Log Info Handler. The manipulation results in improper authorization. The attack can be launched remotely. The exploit has been made public and could be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.

Impact

The vulnerability allows unauthorized remote access and manipulation of log information, which can severely impact an organization's ability to monitor and audit system activities. Unauthorized deletion or alteration of logs can hinder incident detection and response, potentially allowing attackers to cover their tracks after further exploitation. This compromises the integrity and availability of log data, critical for compliance and security operations. Organizations relying on yeqifu warehouse for log management may face increased risk of insider threats or external attackers escalating their access or hiding malicious activities. The medium severity rating indicates moderate risk, but the presence of public exploits raises the likelihood of exploitation, especially in environments where access controls are weak or where attackers have limited user privileges. The absence of vendor patches prolongs exposure, increasing the window of opportunity for attackers.

Summary

CVE-2026-2107 is an improper authorization vulnerability discovered in the yeqifu warehouse software, specifically within the Log Info Handler component's controller class (LoginfoController.java). The affected functions—loadAllLoginfo, deleteLoginfo, and batchDeleteLoginfo—do not properly enforce authorization checks, allowing attackers to remotely invoke these functions without sufficient privilege verification. This means an attacker with limited privileges (PR:L) can remotely access or delete log information that should be restricted. The vulnerability does not require user interaction (UI:N) and can be exploited over the network (AV:N) with low attack complexity (AC:L). The CVSS 4.0 score of 5.3 reflects a medium severity, considering the limited privileges required but the potential impact on confidentiality, integrity, and availability of log data. The product does not use versioning, making it difficult to determine all affected versions. The vulnerability was responsibly disclosed early, but the vendor has not yet issued a patch or response. Public exploit code is available, increasing the risk of exploitation, although no active exploitation has been reported. The lack of proper authorization checks in log management functions could allow attackers to manipulate or delete critical audit logs, undermining system monitoring and forensic capabilities.

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