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

CVE-2026-2078: yeqifu warehouse · Improper Authorization

Affects yeqifu warehouseSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 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: 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-25.

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

Organizations should immediately audit and restrict access to the permission management functions within yeqifu warehouse, ensuring only trusted administrators have the necessary privileges. Implement network segmentation and firewall rules to limit remote access to the affected components. Monitor logs for unusual permission changes or access patterns indicative of exploitation attempts. Employ application-layer access controls or web application firewalls (WAFs) to detect and block unauthorized API calls targeting permission functions. Stay alert for vendor updates or community patches and plan for rapid deployment once available. Conduct regular security assessments and penetration tests focusing on authorization controls in the warehouse system. Finally, educate administrators about the risk and signs of exploitation to improve incident response readiness.

Description

A vulnerability was detected in yeqifu warehouse up to aaf29962ba407d22d991781de28796ee7b4670e4. This affects the function addPermission/updatePermission/deletePermission of the file dataset\repos\warehouse\src\main\java\com\yeqifu\sys\controller\PermissionController.java of the component Permission Management. Performing a manipulation results in improper authorization. The attack may be initiated remotely. The exploit is now public and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is 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 limited privileges to alter permission settings remotely, potentially escalating their access rights or disrupting permission configurations. This can lead to unauthorized data access, modification, or deletion, impacting confidentiality and integrity. Availability may also be affected if critical permissions are revoked or altered, causing denial of service to legitimate users. Organizations relying on yeqifu warehouse for permission management in their supply chain or warehouse operations could face operational disruptions, data breaches, or compliance violations. The public availability of exploit code increases the likelihood of targeted attacks, especially in environments where patching is delayed due to the rolling release model. The lack of vendor response and patch availability further exacerbates the risk, requiring organizations to implement compensating controls proactively.

Summary

CVE-2026-2078 identifies an improper authorization vulnerability in the yeqifu warehouse software, specifically within the Permission Management component's controller class (PermissionController.java). The affected functions—addPermission, updatePermission, and deletePermission—fail to enforce proper authorization checks, allowing an attacker with limited privileges to remotely manipulate permissions without requiring user interaction or higher-level authentication. This vulnerability could enable unauthorized modification of access controls, potentially leading to privilege escalation or unauthorized data access. The vulnerability is present up to commit aaf29962ba407d22d991781de28796ee7b4670e4, but due to the product's rolling release model, exact affected versions are difficult to pinpoint. The CVSS 4.0 base score is 5.3 (medium), reflecting the ease of remote exploitation without user interaction but requiring some privilege level. The vendor has been notified but has not yet responded or issued a patch. Public exploit code is available, increasing the risk of exploitation. The vulnerability impacts confidentiality, integrity, and availability to a limited degree, primarily through unauthorized permission changes that could disrupt normal operations or expose sensitive data.

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