How severe is CVE-2014-8350?

No CVSS score has been assigned to CVE-2014-8350 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-8350?

CVE-2014-8350 affects the following packages: smarty/smarty (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2014-8350?

Update smarty/smarty to 3.1.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-8350 is resolved across your whole dependency graph.

How do I detect CVE-2014-8350 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for smarty/smarty, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-8350 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2014-8350 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-8350, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-8350?

CVE-2014-8350 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th 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.

What type of vulnerability is CVE-2014-8350?

CVE-2014-8350 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2014-8350 published, and has it been updated?

CVE-2014-8350 was published on November 3, 2014 and was last updated on April 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2014-8350 — smarty

CVE-2014-8350 is a Code Injection vulnerability in smarty/smarty. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for smarty/smarty — see the affected versions and patch details below.

Smarty arbitrary PHP code execution

Also known asGHSA-2pmx-6mm6-6v72

Published

Nov 3, 2014

Updated

Apr 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘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

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`smarty/smarty`	all versions	3.1.21`composer require smarty/smarty:^3.1.21`

Affected Products

1 product · 100 configurations

Application

smartysmarty

≤ 3.1.20

83 versions

1.01.0a1.0b1.1.01.2.01.2.11.2.21.3.01.3.11.3.21.4.01.4.1

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Smarty before 3.1.21 allows remote attackers to bypass the secure mode r…

bugs.debian.orgNVDSep 2017

Report on seclists.org

seclists.orgNVDSep 2017

Report on seclists.org

seclists.orgNVDSep 2017

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update smarty/smarty to 3.1.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-8350 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2014-8350 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works