CVE-2025-14051
Youlai-Mall 1.0.0 … 2.0.0
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2025-14051 is a low-severity Improper Control of Dynamically-Managed Code Resources (CWE-913) vulnerability in Youlai Youlai-Mall. Its CVSS base score is 2.1 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique Reflective Code Loading (T1620); ranked at the 38th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-6 (Least Privilege) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-14051 is a vulnerability in youlaitech youlai-mall versions 1.0.0 and 2.0.0, affecting the functions getById, updateAddress, and deleteAddress within the file /mall-ums/app-api/v1/addresses/. The flaw stems from improper control of dynamically-identified variables, mapped to CWE-913 and CWE-914.
The vulnerability enables remote exploitation (AV:N) with low attack complexity (AC:L), requiring low privileges (PR:L) and no user interaction (UI:N). Successful attacks can result in low impacts to confidentiality, integrity, and availability (C:L/I:L/A:L), yielding a CVSS v3.1 base score of 6.3.
Advisories on VulDB and related GitHub issues document the issue, noting that an exploit has been published and is available for use. The vendor was contacted early regarding disclosure but provided no response, with no patches or official mitigations referenced.
Notable context includes the public availability of the exploit, which may facilitate real-world attacks against unpatched instances.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-201314
Vulnerability Data
A flaw has been found in youlaitech youlai-mall 1.0.0/2.0.0. Affected is the function getById/updateAddress/deleteAddress of the file /mall-ums/app-api/v1/addresses/. Executing manipulation can lead to improper control of dynamically-identified variables. The attack can be executed remotely. The exploit has been published and…
more
may be used. The vendor was contacted early about this disclosure but did not respond in any way.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 2 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Access enforcement directly stops unauthorized reads/writes to dynamic code resources by applying authorization checks at access time.
Least privilege reduces the set of subjects that can reach or modify dynamic code resources, limiting the weakness's reach.
Isolating security functions from non-security code prevents unintended manipulation of dynamically managed executable resources.
Process isolation keeps each process's dynamic code resources in separate domains, blocking cross-process tampering.
Input validation on variable identifiers stops malformed or unauthorized dynamic names from being used.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices explicitly include controls that prevent improper handling of dynamic code resources.
Blocking unauthorized code execution directly limits the ability to abuse dynamically-managed resources.
Runtime-environment monitoring can detect exploitation of the weakness but does not prevent it.
Vulnerability identification can surface instances of CWE-913 but does not mitigate the root weakness.
Hardened configuration baselines can restrict dynamic code execution and variable access at runtime.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect dynamic code weaknesses but does not prevent them at design or coding time.
Secure development lifecycle mandates controls on dynamic code generation and resource management.
Application security requirements explicitly address restrictions on dynamic code execution and resource access.
Secure architecture principles require design controls that prevent improper dynamic code resource manipulation.
Secure coding standards directly prohibit unsafe dynamic code resource handling and injection patterns.
Information access restriction limits variable scope but does not address dynamic identification itself.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Windows 10 (1 rule)
- V-220726 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913
Windows 11 (1 rule)
- V-253283 Data Execution Prevention (DEP) must be configured to at least OptOut. prevents CWE-913