CVE-2025-52130
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:NSummary
CVE-2025-52130 is a medium-severity PHP (CWE-616) vulnerability. Its CVSS base score is 5.4 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-25746
Vulnerability Data
File upload vulnerability in WebErpMesv2 1.17 in the app/Http/Controllers/FactoryController.php controller. This flaw allows an authenticated attacker to upload arbitrary files, including PHP scripts, which can be accessed via direct GET requests, potentially resulting in remote code execution (RCE) on the…
more
web server.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Engineering principles such as complete mediation and least privilege require the use of the canonical $_FILES array rather than attacker-writable globals.
Proper validation of all file-upload inputs stops attackers from supplying or overwriting the legacy global variables that the flawed code relies on.
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 directly prevent use of the deprecated PHP upload globals and variable-overwrite flaws.
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 in development can detect the legacy upload pattern before deployment.
Secure development lifecycle mandates proper input handling and file-upload validation, directly addressing the outdated global-variable approach.
Application security requirements include secure file-upload mechanisms that eliminate reliance on the four legacy PHP variables.
Secure architecture principles discourage unsafe global state, indirectly reducing exposure to variable-injection attacks.
Secure coding explicitly prohibits use of deprecated upload variables and requires validated, server-side file handling.