Advisory record · GHSA-9m49-vhwv-422g

Smarty PHP code injection

CVSS 9.8 CriticalCriticalEPSS 0.031 · 88th percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 14 May 2022, 03:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
smarty/smartyPackagist>=3, <3.1.323.1.32
Identifiers
GHSA-9m49-vhwv-422g · CVE-2017-1000480 · PKSA-m8bd-7wwg-qgrb
Weakness (CWE)
CWE-94
Published
14 May 2022
Updated
24 Apr 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Smarty versions 3 before 3.1.32 are vulnerable to PHP code injection when fetch() or display() is called on custom resources that do not sanitize the template name. The source gives few details on who can trigger it or how far an attacker could go. Upgrade smarty/smarty to 3.1.32 or later.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS 0.031, the 88th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:30 UTC First seen by agentprime
  2. 31 Oct 2026, 14:30 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.