GHSA-hwq7-5vv9-c6cf
MEDIUMGHSA-hwq7-5vv9-c6cf is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in smarty/smarty. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-hwq7-5vv9-c6cf is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Smarty Cross-site Scripting vulnerability in pages that use smarty_function_mailto
Blast Radius
smarty/smarty🐘smarty/smartyReal-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
In Smarty before 3.1.47 and 4.x before 4.2.1, libs/plugins/function.mailto.php allows cross-site scripting. A web page that uses smarty_function_mailto, and that could be parameterized using GET or POST input parameters, could allow injection of JavaScript code by a user.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | smarty/smarty | all versions | 3.1.47 |
| 🐘Packagist | smarty/smarty | ≥ 4.0.0&&< 4.2.1 | 4.2.1 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty. 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 smarty/smarty to 3.1.47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hwq7-5vv9-c6cf 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-hwq7-5vv9-c6cf 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-hwq7-5vv9-c6cf. 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-hwq7-5vv9-c6cf in your dependencies?
O3 detects GHSA-hwq7-5vv9-c6cf across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.