How severe is CVE-2005-0913?

CVE-2005-0913 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2005-0913 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2005-0913?

CVE-2005-0913 primarily affects Smarty. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2005-0913?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2005-0913 published?

CVE-2005-0913 was published on 2005-05-02 and last updated on 2026-06-16.

CVE-2005-0913

CVE-2005-0913 is a high-severity vulnerability in Smarty with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 2% (72nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Smarty
Published: 2005-05-02
Last modified: 2026-06-16

Description

Unknown vulnerability in the regex_replace modifier (modifier.regex_replace.php) in Smarty before 2.6.8 allows attackers to execute arbitrary PHP code.

Frequently asked questions

What is CVE-2005-0913?: Unknown vulnerability in the regex_replace modifier (modifier.regex_replace.php) in Smarty before 2.6.8 allows attackers to execute arbitrary PHP code.
How severe is CVE-2005-0913?: CVE-2005-0913 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2005-0913 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (72nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2005-0913?: CVE-2005-0913 primarily affects Smarty. In total, 6 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2005-0913?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2005-0913 published?: CVE-2005-0913 was published on 2005-05-02 and last updated on 2026-06-16.

References

Affected products (6)

cpe:2.3:a:smarty:smarty:2.6.2:*:*:*:*:*:*:*
cpe:2.3:a:smarty:smarty:2.6.3:*:*:*:*:*:*:*
cpe:2.3:a:smarty:smarty:2.6.4:*:*:*:*:*:*:*
cpe:2.3:a:smarty:smarty:2.6.5:*:*:*:*:*:*:*
cpe:2.3:a:smarty:smarty:2.6.6:*:*:*:*:*:*:*
cpe:2.3:a:smarty:smarty:2.6.7:*:*:*:*:*:*:*

More vulnerabilities in Smarty

CVE-2010-4727 — Critical (CVSS 10.0): Smarty before 3.0.0 beta 7 does not properly handle the <?php and ?> tags, which has unspecified impact and remote…
CVE-2010-4726 — Critical (CVSS 10.0): Unspecified vulnerability in the math plugin in Smarty before 3.0.0 RC1 has unknown impact and remote attack vectors.…
CVE-2010-4725 — Critical (CVSS 10.0): 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…
CVE-2010-4724 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in the parser implementation in Smarty before 3.0.0 RC3 have unknown impact and…
CVE-2010-4722 — Critical (CVSS 10.0): Unspecified vulnerability in the fetch plugin in Smarty before 3.0.2 has unknown impact and remote attack vectors.
CVE-2009-5052 — Critical (CVSS 10.0): Multiple unspecified vulnerabilities in Smarty before 3.0.0 beta 6 have unknown impact and attack vectors.

All CVEs affecting Smarty →