Bagisto has Normal & Blind SSTI from low-privilege user when ordering productGHSA-5j4h-4f72-qpm6
CRITICALGHSA-5j4h-4f72-qpm6 is a critical-severity (CVSS 9.8) CWE-1336 vulnerability in bagisto/bagisto. A fix is available for bagisto/bagisto — see the affected versions and patch details below.
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.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-5j4h-4f72-qpm6.
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
bagisto/bagistoReal-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
SSTI when normal customer orders any product in add address step can inject value run in admin view.
Details
As normal user
- Go to
http://127.0.0.1:8000/ - Add order to cart and continue to checkout
- In step of add address inject this value {{7*7}} in any input
As admin
- Go to
http://127.0.0.1:8000/admin/sales/orders - And notice the vlaue appear in admin view 49
As normal user
3. Go to add address normally http://127.0.0.1:8000/customer/account/addresses/create and inject {{7*7}} on it and will notice it appear 49
<img width="1868" height="868" alt="image" src="https://github.com/user-attachments/assets/279627e9-6361-4d39-a500-0fc20e163d25" />
PoC
- Video attached with the report: https://github.com/user-attachments/assets/a814b30c-a3e2-4a40-8644-336e21e60d0d
Impact
- Can lead to RCE
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | bagisto/bagisto | all versions | 2.3.10composer require bagisto/bagisto:^2.3.10 |
Affected Products
bagistowebkulDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for bagisto/bagisto, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update bagisto/bagisto to 2.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5j4h-4f72-qpm6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-5j4h-4f72-qpm6 in your dependencies?
Find it across Packagist, including transitive dependencies.