UnoPim Stored XSS : Cookie hijacking through Create User function

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2024-52305: 0.20% estimated exploitation activity in the next 30 days; percentile 9.53 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 1. Login as admin 2. Go to Create User 3. Fill up everything in the registration form then upload SVG image as a profile picture 4. In SVG image, add script tag to prepare for XSS attack 5. Complete the Create User process 6. Right click at the image to obtain image URL address 7. 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.

Published by the source

13 Nov 2024, 18:37 UTC

Last modified by the source

13 Nov 2024, 18:37 UTC

Source last checked

26 Oct 2026, 14:28 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-cgr4-c233-h733

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-52305

Advisory: UnoPim Stored XSS : Cookie hijacking through Create User function
IDs: CVE-2024-52305, GHSA-cgr4-c233-h733
Record: https://patchnext.com/advisories/cve-2024-52305 (revision 1, source checked 26 Oct 2026, 14:28 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: unopim/unopim 0.1.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist unopim/unopim: affected < 0.1.5; fixed in 0.1.5

## Suggested inspection (read-only)
- Packagist unopim/unopim: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on unopim/unopim.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cgr4-c233-h733 (GitHub-reviewed advisory GHSA-cgr4-c233-h733 lists affected ranges: Packagist unopim/unopim >=0 <0.1.5)

Commands are suggestions: review each one before running it.