GHSA-px8v-hxxx-2rgh is a high-severity (CVSS 7.4) Code Injection vulnerability in barrelstrength/sprout-base-email. O3 Security confirms whether GHSA-px8v-hxxx-2rgh is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Potential Code Injection in Sprout Forms
Real-World Exposure
barrelstrength/sprout-base-email🐘barrelstrength/sprout-formsReal-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
Impact
A potential Server-Side Template Injection vulnerability exists in Sprout Forms which could lead to the execution of Twig code.
Patches
The problem is fixed inbarrelstrength/sprout-forms:v3.9.0 which upgrades to barrelstrength/sprout-base-email:v1.2.7
Workarounds
Users unable to upgrade should update any Notification Emails to use the "Basic Notification (Sprout Email)" template and avoid using the "Basic Notification (Sprout Forms)" template or any custom templates that display Form Fields.
References
- See the release notes in the CHANGELOG
- Credits to Paweł Hałdrzyński, Daniel Kalinowski from ISEC.PL for discovery and responsible disclosure
For more information
If you have any questions or comments about this advisory:
- Open an issue in the Sprout Forms repo
- Email us at [email protected]
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | barrelstrength/sprout-base-email | all versions | 1.2.7 |
| 🐘Packagist | barrelstrength/sprout-forms | all versions | 3.9.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for barrelstrength/sprout-base-email. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update barrelstrength/sprout-base-email to 1.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-px8v-hxxx-2rgh 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.
How O3 protects you
O3 pinpoints whether GHSA-px8v-hxxx-2rgh is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-px8v-hxxx-2rgh. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-px8v-hxxx-2rgh in your dependencies?
O3 detects GHSA-px8v-hxxx-2rgh across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.