high CVSS 7.5

CVE-2025-14180·PHP vulnerability

In PHP versions 8.1.* before 8.1.34, 8.2.* before 8.2.30, 8.3.* before 8.3.29, 8.4.* before 8.4.16, 8.5.* before 8.5.1 when using the PDO PostgreSQL driver with PDO::ATTR_EMULATE_PREPARES enabled, an invalid character sequence (such as \x99) in a prepared statement parameter may cause the quoting function PQescapeStringConn to return NULL, leading to a null pointer dereference in pdo_parse_params() function. This may lead to crashes (segmentation fault) and affect the availability of the target server.

Severity
high
Software
PHP
Fixed in
8.5.1
Published
2025-12-27

Affected versions

From: 8.5.0

Until: 8.5.1

Fixed in: 8.5.1

How to fix this CVE

Upgrade PHP to version 8.5.1 or later to resolve this denial-of-service vulnerability in the PDO PostgreSQL driver. If you are running PHP 8.1, 8.2, 8.3, or 8.4, apply the corresponding security updates (8.1.34+, 8.2.30+, 8.3.29+, or 8.4.16+ respectively). Ensure PDO::ATTR_EMULATE_PREPARES is disabled in your PDO configuration when possible, as this setting increases the risk surface for this issue.

sudo dnf update php

Defensia detects this vulnerability

How to check if you are affected

  1. Run `php -v` to verify your current PHP version and check if it falls within the vulnerable ranges: 8.1.x < 8.1.34, 8.2.x < 8.2.30, 8.3.x < 8.3.29, 8.4.x < 8.4.16, or 8.5.0
  2. Check your PHP configuration with `php -i | grep -i pdo.pgsql` and verify whether PDO::ATTR_EMULATE_PREPARES is explicitly enabled in your application code or php.ini
  3. Search application error logs for segmentation fault messages ("Segmentation fault" or "SIGSEGV") that occur during database query processing, particularly in PDO PostgreSQL contexts
  4. After upgrading, run `php -v` again to confirm the patched version is active, then restart PHP-FPM or your web server with `sudo systemctl restart php-fpm` or `sudo systemctl restart apache2/nginx`

FAQ

What is CVE-2025-14180?

This is a denial-of-service vulnerability in PHP's PDO PostgreSQL driver where certain invalid byte sequences in prepared statement parameters cause a null pointer dereference, resulting in application crashes (segmentation faults). The issue only occurs when PDO::ATTR_EMULATE_PREPARES is enabled.

Is CVE-2025-14180 being actively exploited?

No, this vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available.

What versions of PHP are affected by CVE-2025-14180?

PHP 8.1.0 through 8.1.33, 8.2.0 through 8.2.29, 8.3.0 through 8.3.28, 8.4.0 through 8.4.15, and 8.5.0 are vulnerable. PHP 8.5.1 and later patch versions in other release lines resolve the issue.

How do I check if my server is vulnerable to CVE-2025-14180?

Run `php -v` to check your version number. If it matches one of the vulnerable ranges listed above and your application uses PDO with PostgreSQL while enabling PDO::ATTR_EMULATE_PREPARES, your server is at risk.

Does Defensia detect CVE-2025-14180?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If PHP is installed on a monitored server, CVE-2025-14180 will appear in your dashboard with remediation steps.

Related PHP CVEs

CVE-2024-5932CVSS 10The GiveWP – Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.14.1 via deserialization of untrusted input from the 'give_title' parameter. This makes it possible for unauthenticated attackers to inject a PHP Object. The additional presence of a POP chain allows attackers to execute code remotely, and to delete arbitrary files.
CVE-2026-39337CVSS 10ChurchCRM is an open-source church management system. Prior to 7.1.0, critical pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The "$dbPassword" variable is not sanitized. This vulnerability exists due to an incomplete fix for CVE-2025-62521. This vulnerability is fixed in 7.1.0.
CVE-2025-62521CVSS 10ChurchCRM is an open-source church management system. Prior to version 5.21.0, a pre-authentication remote code execution vulnerability in ChurchCRM's setup wizard allows unauthenticated attackers to inject arbitrary PHP code during the initial installation process, leading to complete server compromise. The vulnerability exists in `setup/routes/setup.php` where user input from the setup form is directly concatenated into a PHP configuration template without any validation or sanitization. Any parameter in the setup form can be used to inject PHP code that gets written to `Include/Config.php`, which is then executed on every page load. This is more severe than typical authenticated RCE vulnerabilities because it requires no credentials and affects the installation process that administrators must complete. Version 5.21.0 patches the issue.
CVE-2025-25174CVSS 10Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 BeeTeam368 Extensions beeteam368-extensions allows PHP Local File Inclusion.This issue affects BeeTeam368 Extensions: from n/a through <= 1.9.4.
CVE-2026-28289CVSS 10FreeScout is a free help desk and shared inbox built with PHP's Laravel framework. A patch bypass vulnerability for CVE-2026-27636 in FreeScout 1.8.206 and earlier allows any authenticated user with file upload permissions to achieve Remote Code Execution (RCE) on the server by uploading a malicious .htaccess file using a zero-width space character prefix to bypass the security check. The vulnerability exists in the sanitizeUploadedFileName() function in app/Http/Helper.php. The function contains a Time-of-Check to Time-of-Use (TOCTOU) flaw where the dot-prefix check occurs before sanitization removes invisible characters. This vulnerability is fixed in 1.8.207.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2025-14180. Free for 1 server.

Get started free