CVE-2010-4727 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4727): Smarty before 3.0.0 beta 7 does not properly handle the <?php and ?> tags, which has unspecified impact and remote attack vectors. CVE-2010-4726 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4726): 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. CVE-2010-4725 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4725): Smarty before 3.0.0 RC3 does not properly handle an on value of the asp_tags option in the php.ini file, which has unspecified impact and remote attack vectors. CVE-2010-4724 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4724): Multiple unspecified vulnerabilities in the parser implementation in Smarty before 3.0.0 RC3 have unknown impact and remote attack vectors. CVE-2010-4723 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4723): Smarty before 3.0.0, when security is enabled, does not prevent access to the (1) dynamic and (2) private object members of an assigned object, which has unspecified impact and remote attack vectors. CVE-2010-4722 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4722): Unspecified vulnerability in the fetch plugin in Smarty before 3.0.2 has unknown impact and remote attack vectors. CVE-2009-5054 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2009-5054): Smarty before 3.0.0 beta 4 does not consider the umask value when setting the permissions of files, which might allow attackers to bypass intended access restrictions via standard filesystem operations. CVE-2009-5052 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2009-5052): Multiple unspecified vulnerabilities in Smarty before 3.0.0 beta 6 have unknown impact and attack vectors. Could you please check if our stable branch, 2.6.x, is affected at all? If no, that'd great from our side. If yes, we'd have to stabilize 3.0. Would that be possible?
NVD says 2.6.x is affected, and I'm not sure how many of the bugs got fixes backported in 2.6.27 (NVD doesn't list 2.6.27 as affected, but the pages were last updated in 2011 and .27 came out in 2012). I would strongly suggest stabilizing the 3.* branch. @maintainers: your call.
GLSA vote: no.
GLSA vote: no Closing as noglsa, cleanup will be done in bug #435618
