CVE-2024-52305 is a medium-severity (CVSS 6.5) CWE-616 vulnerability in unopim/unopim. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for unopim/unopim — see the affected versions and patch details below.
UnoPim Stored XSS : Cookie hijacking through Create User function
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-52305.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
unopim/unopimReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
Summary
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 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.
Details
- Login as admin
- Go to Create User
- Fill up everything in the registration form then upload SVG image as a profile picture
- In SVG image, add script tag to prepare for XSS attack
- Complete the Create User process
- Right click at the image to obtain image URL address
- XSS triggered
PoC
The below link is a private YouTube video for PoC. https://youtu.be/5j8owD0--1A
Impact
The stored XSS can lead to session hijacking and privilege escalation, effectively bypassing any CSRF protections in place.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | unopim/unopim | all versions | 0.1.5composer require unopim/unopim:^0.1.5 |
Affected Products
unopimwebkulResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for unopim/unopim, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update unopim/unopim to 0.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-52305 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2024-52305 in your dependencies?
Find it across Packagist, including transitive dependencies.