CVE-2024-52305
Webkul Unopim ≤ 0.1.5
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NSummary
CVE-2024-52305 is a medium-severity PHP (CWE-616) vulnerability in Webkul Unopim. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 8th 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 SI-10 (Information Input Validation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-3235
Vulnerability Data
UnoPim is an open-source Product Information Management (PIM) system built on the Laravel framework. A vulnerability exists in the Create User process, allowing the creation of a new admin account with an option to upload a profile image. An attacker…
more
can upload a malicious SVG file containing an embedded script. When the profile image is accessed, the embedded script executes, leading to the potential theft of session cookies. This vulnerability is fixed in 0.1.5.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation requires complete, allowlist-style checks that structurally eliminate reliance on incomplete XSS denylists.
Engineering principles such as complete mediation and least privilege require the use of the canonical $_FILES array rather than attacker-writable globals.
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.