VulnerabilityPublished 25 Dec 2025Updated 26 Feb 2026

CVE-2025-15087: youlaitech youlai-mall · Improper Authorization

Affects youlaitech youlai-mallSource CVE Database V5

Public exploit available · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% 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:N/VI:L/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: None
Vulnerable system integrity: Low
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: None: There is no loss of confidentiality within 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: 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: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

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 or the CVSS exploit maturity 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

Organizations should immediately audit and restrict access to the submitOrderPayment function, implementing strict authorization checks to ensure that orderSn parameters correspond only to orders owned by the authenticated user or authorized entity. Network-level protections such as web application firewalls (WAFs) should be configured to detect and block suspicious manipulation of orderSn parameters. Monitoring and logging of order payment submissions should be enhanced to detect anomalous activity. If possible, disable or restrict remote access to the affected endpoints until a vendor patch or official fix is available. Organizations should also consider code review and patching to validate authorization logic rigorously. Engaging with the vendor for updates or applying community-developed patches is recommended. Finally, educating developers on secure coding practices around authorization can prevent similar issues.

Description

A security vulnerability has been detected in youlaitech youlai-mall 1.0.0/2.0.0. Affected is the function submitOrderPayment of the file mall-oms/oms-boot/src/main/java/com/youlai/mall/oms/controller/app/OrderController.java. Such manipulation of the argument orderSn leads to improper authorization. The attack may be launched remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The improper authorization vulnerability in youlai-mall can lead to unauthorized submission or manipulation of order payments, potentially allowing attackers to interfere with financial transactions, cause fraudulent payments, or disrupt order processing. This can result in financial losses, reputational damage, and operational disruption for organizations using the affected platform. Since the vulnerability can be exploited remotely without authentication or user interaction, it poses a significant risk to any exposed youlai-mall installations. The integrity of order data and payment processes is directly impacted, and while availability impact is limited, unauthorized transactions could indirectly cause service disruptions or customer trust issues. Organizations relying on youlai-mall for e-commerce operations are at risk of fraud and operational compromise until the vulnerability is mitigated.

Summary

CVE-2025-15087 is an improper authorization vulnerability found in the youlaitech youlai-mall e-commerce platform, specifically in versions 1.0.0 and 2.0.0. The flaw resides in the submitOrderPayment function within the OrderController.java source file, where the orderSn parameter is insufficiently validated or authorized. This allows an attacker to manipulate the orderSn argument remotely to bypass authorization checks, potentially submitting payment orders on behalf of other users or altering order payment status without proper permissions. The vulnerability requires no user interaction and no prior authentication, increasing its exploitability. The vendor was contacted but has not issued any patches or mitigations. The vulnerability has a CVSS 4.0 base score of 5.3, indicating medium severity, with an attack vector of network, low attack complexity, no privileges required, and no user interaction needed. The impact primarily affects the integrity and potentially the availability of order payment processing within the platform. No known exploits have been observed in the wild yet, but public disclosure increases the risk of exploitation. This vulnerability highlights the importance of robust authorization checks on critical e-commerce functions to prevent unauthorized financial transactions.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 06:25 UTC

Technical details

References

Community reviews

Related threats