716 matches found
CVE-2010-4722
Unspecified vulnerability in the fetch plugin in Smarty before 3.0.2 has unknown impact and remote attack vectors...
Design/Logic Flaw
Multiple unspecified vulnerabilities in Smarty before 3.0.0 beta 6 have unknown impact and attack vectors...
CVE-2009-5053
Unspecified vulnerability in Smarty before 3.0.0 beta 6 allows remote attackers to execute arbitrary PHP code by injecting this code into a cache file...
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...
Design/Logic Flaw
Smarty before 3.0.0 RC3 does not properly handle an on value of the asptags option in the php.ini file, which has unspecified impact and remote attack vectors...
Design/Logic Flaw
Smarty before 3.0.0 beta 7 does not properly handle the tags, which has unspecified impact and remote attack vectors...
CVE-2010-4722
Unspecified vulnerability in the fetch plugin in Smarty before 3.0.2 has unknown impact and remote attack vectors...
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-4725
Smarty before 3.0.0 RC3 has a vulnerability related to how the asp_tags option is handled in php.ini. The issue is triggered by an on value of asp_tags and is described as having unspecified impact with remote attack vectors, but the connected documents do not provide concrete details on affected...
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-2010-4724
CVE-2010-4724 concerns multiple unspecified vulnerabilities in the parser implementation of the Smarty template engine, affecting versions before 3.0.0 RC3. The available sources describe the issues as having unknown impact and remote attack vectors, with no concrete exploitation details or remed...
CVE-2009-5054
Smarty before 3.0.0 beta 4 does not consider the umask value when setting file permissions, which may allow bypass of intended access restrictions via standard filesystem operations. Affected component: Smarty (PHP template engine). Root cause: permissions are assigned without regard to umask, en...
CVE-2010-4726
CVE-2010-4726 corresponds to Smarty’s math plugin vulnerability prior to Smarty 3.0.0 RC1. Connected advisories/entries confirm multiple remote vulnerabilities in Smarty (e.g., CVE-2008-4810, CVE-2009-1669) that could allow remote code execution. Affected component: Smarty templates engine (libs/...
CVE-2010-4727
Smarty before 3.0.0 beta 7 does not properly handle the tags, which has unspecified impact and remote attack vectors...
CVE-2010-4725
Smarty before 3.0.0 RC3 does not properly handle an on value of the asptags option in the php.ini file, which has unspecified impact and remote attack vectors...
CVE-2010-4723
Smarty before 3.0.0, when security is enabled, does not prevent access to the dynamic and private object members of an assigned object. The impact is unspecified in the provided documents, and there are no explicit exploit details or vectors described. No remediation steps are provided in the con...
CVE-2009-5052
Smarty before 3.0.0 beta 6 is affected by multiple unspecified vulnerabilities. The entries consistently cite unknown impact and attack vectors, with no concrete details on root cause, affected components, or exploit paths in the provided documents. The scope is limited to the version boundary “b...
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-2009-5053
Unspecified vulnerability in Smarty before 3.0.0 beta 6 allows remote attackers to execute arbitrary PHP code by injecting this code into a cache file...
CVE-2009-5053
Technical details about CVE-2009-5053 are not publicly provided in the supplied documents. Monitor for updates; current sources do not specify affected products, versions, or remediation within the provided material.