Menu

Star on GitHub · 3.2k

CVE-2010-4727

10.0 · HIGH

Smarty before 3.0.0 beta 7 does not properly handle the <?php and ?> tags, which has unspecified impact and remote attack vectors.

Published Feb 3, 2011smartyCWE-20EPSS 1.88%

Overview

CVE-2010-4727 is a high-severity vulnerability affecting smarty smarty. It was published on February 3, 2011 and has a CVSS 2.0 base score of 10.0 (HIGH).

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Smarty before 3.0.0 beta 7 does not properly handle the <?php and ?> tags, which has unspecified impact and remote attack vectors.

Remediation

Check the references section for vendor advisories and patches from smarty. Update smarty to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus
smartysmarty0Affected

Frequently asked questions

What is CVE-2010-4727?

CVE-2010-4727 is a high-severity vulnerability affecting smarty smarty. It was published on February 3, 2011 and has a CVSS 2.0 base score of 10.0 (HIGH).

How severe is CVE-2010-4727?

This vulnerability has a CVSS 2.0 base score of 10.0, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2010-4727?

Check the references section for vendor advisories and patches from smarty. Update smarty to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2010-4727?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2010-4727 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2010

View all