CVE-2025-15086VulnerabilityPublished 25 Dec 2025Updated 29 Dec 2025

CVE-2025-15086: youlaitech youlai-mall · Improper Access Controls

Affects youlaitech youlai-mallSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 06:26 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:N/VA:N/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: None
Vulnerable system availability: None
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: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within 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 25 Dec 2025
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-26.

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
Mavencom.youlai/mall`pkg:maven/com.youlai/mall`Other threats	Affected =1.0.0 =2.0.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Since no official patches are available from the vendor, European organizations should implement compensating controls immediately. These include restricting network access to the affected API endpoints via firewalls or API gateways, limiting exposure to trusted internal networks only. Implement strict authentication and authorization checks at the application or proxy level to ensure only authorized users can invoke getMemberByMobile or similar functions. Conduct thorough code reviews and, if possible, apply custom patches or overrides to enforce proper access controls. Monitor logs and network traffic for unusual access patterns targeting member data retrieval functions. Employ Web Application Firewalls (WAFs) with rules designed to detect and block exploitation attempts against this endpoint. Educate development teams to prioritize upgrading or replacing youlai-mall versions once vendor patches become available. Finally, prepare incident response plans to quickly address any potential data breach resulting from exploitation.

Description

A weakness has been identified in youlaitech youlai-mall 1.0.0/2.0.0. This impacts the function getMemberByMobile of the file mall-ums/ums-boot/src/main/java/com/youlai/mall/ums/controller/app/MemberController.java. This manipulation causes improper access controls. The attack may be initiated remotely. The exploit has been made available to the public and could be exploited. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

For European organizations using youlai-mall versions 1.0.0 or 2.0.0, this vulnerability poses a risk of unauthorized access to member data, potentially leading to data breaches involving PII. Such breaches could result in regulatory penalties under GDPR due to inadequate protection of personal data. The improper access control could undermine customer trust and damage brand reputation. Although the impact on integrity and availability is minimal, the confidentiality breach alone is significant in sectors handling sensitive customer information, such as retail, finance, or healthcare. The public availability of exploit code increases the likelihood of opportunistic attacks, especially against organizations that have not applied mitigations or workarounds. The absence of vendor patches means organizations must rely on internal controls and monitoring to reduce risk. Additionally, attackers exploiting this vulnerability could use accessed data for further attacks, including social engineering or identity theft, amplifying the overall impact.

Summary

CVE-2025-15086 identifies a security weakness in the youlaitech youlai-mall e-commerce platform, specifically versions 1.0.0 and 2.0.0. The vulnerability resides in the getMemberByMobile function of the MemberController.java source file, which is responsible for retrieving member information based on a mobile number. Due to improper access control implementation, remote attackers can invoke this function without proper authorization, potentially accessing sensitive member data. The vulnerability does not require authentication or user interaction, making it easier to exploit remotely over the network. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L, interpreted as low privileges), no user interaction (UI:N), and low impact on confidentiality (VC:L) with no impact on integrity or availability. The exploit code has been publicly disclosed, increasing the risk of exploitation, although no active exploitation has been reported. The vendor was notified early but has not issued any patches or advisories, leaving users exposed. This vulnerability could allow unauthorized data disclosure of member information, which may include personally identifiable information (PII) or other sensitive data, depending on the implementation of the affected function.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 1 Jan 2026, 22:31 UTC

Technical details

References

Community reviews

Related threats