Skip to content
Fencer Intel
high 7.5

CVE-2014-8350 json

Smarty arbitrary PHP code execution

published 12y ago modified 4mo ago also GHSA-2pmx-6mm6-6v72 , EUVD-2022-2026

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.1%
EPSS 3.1% chance of exploitation in 30 days, percentile 87%
public exploits
0
none known

Summary

Smarty before 3.1.21 allows remote attackers to bypass the secure mode restrictions and execute arbitrary PHP code as demonstrated by "{literal}<{/literal}script language=php>" in a template.

Patch / fix

  • packagist smarty/smarty 3.1.21
  • smarty3 Debian 14, Debian 13, Debian 12 3.1.21-1

debian advisories DEBIAN-CVE-2014-8350

Is CVE-2014-8350 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-8350 updated cvss 6.8

php-Smarty: secure mode bypass

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.13% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • seclists.org http://seclists.org/oss-sec/2014/q4/421 referenced PoC, tagged "exploit" by a source, unverified
  • seclists.org http://seclists.org/oss-sec/2014/q4/420 referenced PoC, tagged "exploit" by a source, unverified
  • bugs.debian.org https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765920 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected packages

ecosystem package affected fixed in
packagist smarty/smarty
<3.1.21
3.1.21

Classification

Weakness
  • CWE-94 Improper Control of Generation of Code

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.