First published: Thu Feb 03 2011(Updated: )
Unspecified vulnerability in the math plugin in Smarty before 3.0.0 RC1 has unknown impact and remote attack vectors. NOTE: this might overlap CVE-2009-1669.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Smarty | =1.4.3 | |
Smarty | =1.0 | |
Smarty | =1.0b | |
Smarty | =2.3.1 | |
Smarty | =3.0.0-beta6 | |
Smarty | =2.6.0-rc3 | |
Smarty | =2.6.25 | |
Smarty | =1.4.0 | |
Smarty | =1.4.5 | |
Smarty | =2.6.1 | |
Smarty | =2.6.7 | |
Smarty | =2.6.20 | |
Smarty | =2.3.0 | |
Smarty | =1.0a | |
Smarty | =1.1.0 | |
Smarty | =1.4.0-b2 | |
Smarty | =2.6.0 | |
Smarty | =2.6.15 | |
Smarty | =2.6.3 | |
Smarty | =2.6.14 | |
Smarty | =2.5.0-rc1 | |
Smarty | =1.2.1 | |
Smarty | =2.6.17 | |
Smarty | =2.6.11 | |
Smarty | =2.6.0-rc2 | |
Smarty | =3.0.0-beta7 | |
Smarty | =1.3.0 | |
Smarty | =1.4.1 | |
Smarty | =2.5.0-rc2 | |
Smarty | =2.0.1 | |
Smarty | =2.5.0 | |
Smarty | =1.4.2 | |
Smarty | =1.5.0 | |
Smarty | =2.1.0 | |
Smarty | =2.6.22 | |
Smarty | =1.5.2 | |
Smarty | =2.6.12 | |
Smarty | =2.6.18 | |
Smarty | =1.5.1 | |
Smarty | =2.0.0 | |
Smarty | =2.4.1 | |
Smarty | =2.6.6 | |
Smarty | <=3.0.0 | |
Smarty | =2.6.26 | |
Smarty | =2.6.16 | |
Smarty | =2.6.9 | |
Smarty | =1.2.2 | |
Smarty | =3.0.0-beta5 | |
Smarty | =2.6.0-rc1 | |
Smarty | =2.6.24 | |
Smarty | =2.1.1 | |
Smarty | =2.6.4 | |
Smarty | =2.2.0 | |
Smarty | =2.4.2 | |
Smarty | =2.6.10 | |
Smarty | =2.6.2 | |
Smarty | =1.4.0-b1 | |
Smarty | =2.6.13 | |
Smarty | =3.0.0-beta4 | |
Smarty | =2.6.5 | |
Smarty | =1.3.2 | |
Smarty | =2.4.0 | |
Smarty | =1.3.1 | |
Smarty | =1.4.4 | |
Smarty | =1.4.6 | |
Smarty | =1.2.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2010-4726 is currently unknown as it has unspecified impacts and remote attack vectors.
To fix CVE-2010-4726, upgrade to Smarty version 3.0.0 RC1 or later.
CVE-2010-4726 affects multiple versions of Smarty up to and including 3.0.0 beta7.
Yes, CVE-2010-4726 may have remote attack vectors allowing potential exploitation from afar.
Yes, CVE-2010-4726 may overlap with CVE-2009-1669.