CVE-2026-2078

6.3 MEDIUM

📋 TL;DR

This CVE describes an improper authorization vulnerability in yeqifu warehouse's permission management functions. Attackers can remotely manipulate permissions (add/update/delete) without proper authorization, potentially gaining unauthorized access or privileges. All users of yeqifu warehouse up to commit aaf29962ba407d22d991781de28796ee7b4670e4 are affected.

💻 Affected Systems

Products:
  • yeqifu warehouse
Versions: All versions up to commit aaf29962ba407d22d991781de28796ee7b4670e4
Operating Systems: Any OS running yeqifu warehouse
Default Config Vulnerable: ⚠️ Yes
Notes: This product uses a rolling release model, making specific version tracking difficult. The vulnerability exists in the permission management component.

⚠️ Manual Verification Required

This CVE does not have specific version information in our database, so automatic vulnerability detection cannot determine if your system is affected.

Why? The CVE database entry doesn't specify which versions are vulnerable (no version ranges provided by the vendor/NVD).

🔒 Custom verification scripts are available for registered users. Sign up free to download automated test scripts.

Recommended Actions:
  1. Review the CVE details at NVD
  2. Check vendor security advisories for your specific version
  3. Test if the vulnerability is exploitable in your environment
  4. Consider updating to the latest version as a precaution

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise where attackers gain administrative privileges, modify all permissions, and potentially access sensitive data or disrupt operations.

🟠

Likely Case

Unauthorized privilege escalation allowing attackers to modify user permissions, potentially gaining access to restricted functionality or data.

🟢

If Mitigated

Limited impact with proper network segmentation and authentication controls, potentially only affecting non-critical systems.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

Public PoC: ⚠️ Yes
Weaponized: LIKELY
Unauthenticated Exploit: ✅ No
Complexity: LOW

The exploit is public and may be used. Attack requires some level of access but not necessarily authentication to the permission management functions.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Monitor the GitHub repository for updates: https://github.com/yeqifu/warehouse/

🔧 Temporary Workarounds

Network Access Restriction

all

Restrict network access to the permission management endpoints to authorized IPs only

# Use firewall rules to restrict access to /permission endpoints
# Example: iptables -A INPUT -p tcp --dport [APP_PORT] -s [TRUSTED_IPS] -j ACCEPT

Authentication Enforcement

all

Ensure all permission management endpoints require proper authentication

# Review and enforce authentication middleware on all /permission routes
# Check that @PreAuthorize or similar annotations are properly configured

🧯 If You Can't Patch

  • Implement strict network segmentation to isolate the warehouse application from untrusted networks
  • Deploy a web application firewall (WAF) with rules to detect and block permission manipulation attempts

🔍 How to Verify

Check if Vulnerable:

Check if your yeqifu warehouse commit hash is aaf29962ba407d22d991781de28796ee7b4670e4 or earlier. Review PermissionController.java for missing authorization checks on addPermission/updatePermission/deletePermission methods.

Check Version:

git log --oneline -1

Verify Fix Applied:

Verify that proper authorization checks (e.g., @PreAuthorize annotations) are implemented on all permission management endpoints in PermissionController.java

📡 Detection & Monitoring

Log Indicators:

  • Unusual permission modification events
  • Multiple failed authorization attempts followed by successful permission changes
  • Requests to /permission endpoints from unexpected sources

Network Indicators:

  • Unusual traffic patterns to permission management endpoints
  • POST/PUT/DELETE requests to /permission without proper authentication headers

SIEM Query:

source="yeqifu-warehouse" AND (uri_path="/permission" OR uri_path="/permission/*") AND (http_method="POST" OR http_method="PUT" OR http_method="DELETE")

🔗 References

📤 Share & Export