Skip to content
Fencer Vulns
critical 10.0

CVE-2009-1669 in the critical feed json

The smarty_function_math function in libs/plugins/function.math.php in Smarty 2.6.22 allows context-dependent attackers to execute arbitrar…

published 2009-05-18 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1664

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
14.1%
EPSS 14.1% chance of exploitation in 30 days, percentile 96%
public exploits
1
Exploit-DB

Summary

The smarty_function_math function in libs/plugins/function.math.php in Smarty 2.6.22 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in the equation attribute of the math function. NOTE: some of these details are obtained from third party information.

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-2009-1669 updated

Smarty: arbitrary commands execution via shell metacharacters in the equation attribute of the math function

  • 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

Timeline

  1. First public exploit (EDB-8659)
  2. Published

Exploit prediction

14.12% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-8659 Bitweaver 2.6 - 'saveFeed()' Remote Code Execution webapps, 2009-05-12
  • securityfocus.com http://www.securityfocus.com/bid/34918 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Vulns 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.