Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-2107: Improper Authorization in yeqifu warehouse

0
Medium
VulnerabilityCVE-2026-2107cvecve-2026-2107
Published: Sat Feb 07 2026 (02/07/2026, 18:32:08 UTC)
Source: CVE Database V5
Vendor/Project: yeqifu
Product: warehouse

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/23/2026, 21:27:43 UTC

Technical Analysis

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.

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

Mitigation Recommendations

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. Since no official patch is available, consider deploying compensating controls such as additional authentication layers or proxying requests through secure gateways that enforce authorization. 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.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-06T14:16:03.665Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 69878bc3f9fa50a62f720652

Added to database: 2/7/2026, 7:00:19 PM

Last enriched: 2/23/2026, 9:27:43 PM

Last updated: 3/25/2026, 6:15:44 AM

Views: 48

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses