CVE-2025-14086

6.3 MEDIUM

📋 TL;DR

This vulnerability in youlaitech youlai-mall allows attackers to bypass access controls by manipulating the openid parameter in the /app-api/v1/members/openid/ endpoint. Attackers can exploit this remotely to gain unauthorized access to user data or system functions. All users running youlai-mall versions 1.0.0 or 2.0.0 are affected.

💻 Affected Systems

Products:
  • youlaitech youlai-mall
Versions: 1.0.0, 2.0.0
Operating Systems: All
Default Config Vulnerable: ⚠️ Yes
Notes: Affects the web application's API endpoint specifically. No specific OS requirements mentioned.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete system compromise allowing unauthorized access to all user accounts, data theft, and potential privilege escalation to administrative functions.

🟠

Likely Case

Unauthorized access to user data, account takeover, and potential manipulation of user information through the vulnerable endpoint.

🟢

If Mitigated

No impact if proper authentication and authorization controls are implemented and the vulnerable endpoint is properly secured.

🌐 Internet-Facing: HIGH
🏢 Internal Only: MEDIUM

🎯 Exploit Status

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

Exploit details are publicly available and the vulnerability can be exploited remotely without authentication.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Unknown

Vendor Advisory: None available

Restart Required: No

Instructions:

No official patch available. Vendor did not respond to disclosure. Consider workarounds or alternative solutions.

🔧 Temporary Workarounds

Block Vulnerable Endpoint

all

Temporarily block access to the vulnerable /app-api/v1/members/openid/ endpoint using web server or firewall rules.

# Apache: RewriteRule ^/app-api/v1/members/openid/ - [F]
# Nginx: location ~ ^/app-api/v1/members/openid/ { return 403; }
# Firewall: iptables -A INPUT -p tcp --dport 80 -m string --string "/app-api/v1/members/openid/" --algo bm -j DROP

Implement Input Validation

all

Add strict input validation and sanitization for the openid parameter to prevent manipulation.

# In application code, validate openid parameter format and length
# Example: if (!isValidOpenIDFormat($openid)) { return error_response(); }

🧯 If You Can't Patch

  • Implement network segmentation to isolate the vulnerable system from critical assets
  • Deploy a web application firewall (WAF) with rules to detect and block exploitation attempts

🔍 How to Verify

Check if Vulnerable:

Test if you can access /app-api/v1/members/openid/ endpoint with manipulated openid parameters and bypass expected access controls.

Check Version:

Check application configuration files or documentation for version information

Verify Fix Applied:

Verify that the endpoint now properly validates and authorizes requests, rejecting unauthorized openid manipulations.

📡 Detection & Monitoring

Log Indicators:

  • Unusual access patterns to /app-api/v1/members/openid/ endpoint
  • Multiple failed authentication attempts followed by successful access
  • Requests with manipulated openid parameters

Network Indicators:

  • Unusual traffic spikes to the vulnerable endpoint
  • Requests with abnormal openid parameter values or formats

SIEM Query:

source="web_logs" AND uri="/app-api/v1/members/openid/" AND (openid="*" OR status=200) | stats count by src_ip

🔗 References

📤 Share & Export