CVE-2008-5625

CVE-2008-5625 is a high-severity vulnerability in Php 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. The underlying weakness is classified as CWE-264.

Key facts

Description

PHP 5 before 5.2.7 does not enforce the error_log safe_mode restrictions when safe_mode is enabled through a php_admin_flag setting in httpd.conf, which allows context-dependent attackers to write to arbitrary files by placing a "php_value error_log" entry in a .htaccess file.

Frequently asked questions

What is CVE-2008-5625?
PHP 5 before 5.2.7 does not enforce the error_log safe_mode restrictions when safe_mode is enabled through a php_admin_flag setting in httpd.conf, which allows context-dependent attackers to write to arbitrary files by placing a "php_value error_log" entry in a .htaccess file.
How severe is CVE-2008-5625?
CVE-2008-5625 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2008-5625 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 7% (94th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2008-5625?
CVE-2008-5625 primarily affects Php. In total, 27 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2008-5625?
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-2008-5625 published?
CVE-2008-5625 was published on 2008-12-17 and last updated on 2026-06-16.

References

Affected products (27)

More vulnerabilities in Php

All CVEs affecting Php →

Other CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities

Browse all CWE-264 (Permissions, Privileges, and Access Controls) vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE: