How severe is GHSA-4rmg-292m-wg3w?

GHSA-4rmg-292m-wg3w has a CVSS score of 7.3/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-4rmg-292m-wg3w?

GHSA-4rmg-292m-wg3w affects the following packages: smarty/smarty (Packagist), smarty/smarty (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-4rmg-292m-wg3w?

Update smarty/smarty to 5.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rmg-292m-wg3w is resolved across your whole dependency graph.

How do I detect GHSA-4rmg-292m-wg3w in my Packagist dependencies?

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.

How do I mitigate GHSA-4rmg-292m-wg3w if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-4rmg-292m-wg3w?

O3 pinpoints whether GHSA-4rmg-292m-wg3w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-4rmg-292m-wg3w actively exploited in the wild?

No public exploit code has been indexed for GHSA-4rmg-292m-wg3w yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-4rmg-292m-wg3w?

GHSA-4rmg-292m-wg3w has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 39th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-4rmg-292m-wg3w published, and has it been updated?

GHSA-4rmg-292m-wg3w was published on May 29, 2024 and was last updated on November 4, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-4rmg-292m-wg3w

HIGH

Smarty vulnerable to PHP Code Injection by malicious attribute in extends-tag

Also known asCVE-2024-35226

Published

May 29, 2024

Updated

Nov 4, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk39th percentile+0.23%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

🐘smarty/smarty🐘smarty/smarty

Real-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

Template authors could inject php code by choosing a malicous file name for an extends-tag. Users that cannot fully trust template authors should update asap.

Patches

Please upgrade to the most recent version of Smarty v4 or v5. There is no patch for v3.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`smarty/smarty`	≥ 5.0.0&&< 5.1.1	5.1.1
🐘Packagist	`smarty/smarty`	≥ 3.0.0&&< 4.5.3	4.5.3

Detection & mitigation playbook

Open-source dependency

Detect
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 5.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4rmg-292m-wg3w 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-4rmg-292m-wg3w 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-4rmg-292m-wg3w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Template authors could inject php code by choosing a malicous file name for an extends-tag. Users that cannot fully trust template authors should update asap. ### Patches Please upgrade to the most recent version of Smarty v4 or v5. There is no patch for v3.

O3 Security · Impact-Aware SCA

Is GHSA-4rmg-292m-wg3w in your dependencies?

O3 detects GHSA-4rmg-292m-wg3w across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works