CVE-2022-29221Public exploitNetwork attack vector

PHP code execution via unescaped template names

Published May 24, 2022 · Updated Apr 23, 2025

Code injection in Smarty before 3.1.45 and 4.0.0 through 4.1.0 allows attackers to execute arbitrary PHP via crafted template names. The block and include compilers place attacker-controlled block names and include source paths inside generated PHP comments without neutralizing a closing */ sequence, so injected text becomes executable PHP. Reachability requires control over template authorship; successful exploitation runs PHP with the privileges of the hosting application.

CVSS severity8.8
High
EPSS probability4.91%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Code injection in Smarty before 3.1.45 and 4.0.0 through 4.1.0 allows attackers to execute arbitrary PHP via crafted template names. The block and include compilers place attacker-controlled block names and include source paths inside generated PHP comments without neutralizing a closing */ sequence, so injected text becomes executable PHP. Reachability requires control over template authorship; successful exploitation runs PHP with the privileges of the hosting application.

The record

CVE
CVE-2022-29221
Published
May 24, 2022
Updated
Apr 23, 2025
Vendor
Smarty
Product
Smarty
Classifications
CWE-94, T1059
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. May 24, 2022CVE publishedPublication date reported by the CVE source.
  2. Apr 23, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 3.1.45
  2. Affected versionversion=>= 4.0.0, < 4.1.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Smarty · Smartyversion=< 3.1.45; version=>= 4.0.0, < 4.1.1

Published CVSS scores

8.8GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-94Improper Control of Generation of Code ('Code Injection')
T1059Command and Scripting Interpreter

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo