Shopper: same-origin SVG and HTML uploads enable stored XSS and persistent administrator creation
Affects Shopper 2.0.0 up to 2.10.1 and 3.0.0 prereleases beta.1 and beta.2, where back-office users with a content upload permission can upload files. Fixed in 2.10.1 and 3.0.0-beta.3.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 2.10.1, 3.0.0-beta.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Shopper, a headless e-commerce admin panel, is affected in versions 2.0.0 through 2.10.1 and in the 3.0.0 beta prereleases. The flaw lets staff with content-upload permissions store HTML or SVG files that run scripts in an administrator's browser when opened, potentially allowing attackers to create persistent administrator accounts and access customer, order, and settings data.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Shopper is a Headless e-commerce Admin Panel. In versions from 2.0.0 prior to 2.10.1 and in the 3.0.0 prereleases beta.1 and beta.2, authenticated back-office staff with a content-upload permission can store executable media on the administrator's own origin. In the 2.x implementation, relevant upload permissions include `edit_products` or `add_brands`, and `packages/admin/config/media.php` allows `image/svg+xml` in every media collection, including image fields whose image/* validation also accepts SVG. The product files collection in `packages/admin/src/Livewire/Components/Products/Form/Files.php` has no MIME restriction and accepts `text/html` as well. Media is served inline from the `public` disk under `/storage/` with its own content type, without `Content-Disposition: attachment` or a `Content-Security-Policy`. When an administrator opens an uploaded HTML or SVG file, stored script executes in that administrator's session. In 2.x, the script can invoke `packages/admin/src/Livewire/SlideOvers/CreateTeamMember.php`, whose `store()` checks `access_setting` held by the viewing administrator but trusts client-supplied `role_id`, to create a new attacker-controlled administrator with a chosen password. This account persists after the uploaded file is deleted and gives access to customer data, orders, settings, and user/role management; the same script can exfiltrate data or grant permissions to the attacker's account. Direct account creation by the low-privileged uploader is blocked, so exploitation requires the administrator to open the file. The 3.x prerelease line already excludes SVG but still allows executable product files. This issue is fixed in versions 2.10.1 and 3.0.0-beta.3.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- shopperlabs shopper
From 2.0.0 · fixed in 2.10.1; From 3.0.0-beta.1 · fixed in 3.0.0-beta.3
References 8
Questions about CVE-2026-62990
What does this mean?
Uploaded SVG and HTML files are served from the same origin as the admin area, so script inside a file can run when an administrator opens it. That script can create a new administrator account that stays in place after the file is deleted.Source: github.com
Am I affected, and how do I check?
Shopper versions from 2.0.0 up to but not including 2.10.1 are affected, as are the 3.0.0 prereleases beta.1 and beta.2 per the CVE description. The setup involves back-office users holding any content upload permission. Check the installed Shopper version in the project's composer.lock or dependency list.Source: github.com
What should I do about it?
Upgrade to 2.10.1 or later on the 2.x line, or to 3.0.0-beta.3 or later on the 3.0 prerelease line.Source: github.com
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data