Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2025-14180: NULL Pointer Dereference in PHP PDO PostgreSQL Emulated Prepares

Published Dec 27, 2025 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v4
EPSS0.70%54th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
PHP Group
IdentifiersCVE-2025-14180CWE-476 · NULL Pointer Dereference

CVE-2025-14180 is a NULL pointer dereference in PHP PDO parameter parsing when the PostgreSQL driver is used with PDO::ATTR_EMULATE_PREPARES enabled. It affects PHP 8.1 before 8.1.34, 8.2 before 8.2.30, 8.3 before 8.3.29, 8.4 before 8.4.16, and 8.5 before 8.5.1. An invalid multibyte sequence in a bound string parameter causes PostgreSQL's PQescapeStringConn to report a quoting error, after which the driver's quoting routine returns NULL. The pdo_parse_params() function subsequently accesses that value through ZSTR_LEN(plc->quoted) without an adequate NULL check, causing a segmentation fault and terminating the PHP process.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation terminates the PHP process handling the malicious parameter, interrupting request processing and reducing application availability. Repeated triggering can cause denial of service. In workflows that commit changes before executing the affected statement, process termination can also leave partially completed operations and inconsistent application state; this behavior has been demonstrated with autocommit enabled. Code execution or sensitive-memory disclosure is not established for this vulnerability.

Mitigation

If you can’t patch tonight, do this now.

Disable PDO::ATTR_EMULATE_PREPARES for affected PostgreSQL connections and use native prepared statements, which are the pdo_pgsql default. Verify that application or framework configuration does not re-enable emulation. This avoids the vulnerable emulated-parameter quoting path pending an upgrade.

Remediation

Patch, then assume compromise.

Upgrade PHP to 8.1.34, 8.2.30, 8.3.29, 8.4.16, 8.5.1, or a later supported release containing the fix. For Debian-packaged deployments, fixed versions include php8.2 8.2.30-1~deb12u1 for bookworm and php8.4 8.4.16-1~deb13u1 for trixie. Update embedded or buildpack-provided PHP runtimes as applicable and ensure deployed applications use the patched runtime.

Public exploits

Exploits

1 exploit validated by Mallory's analysis.

View more in app →
PHP_8.1.x_ExploitThis repository is a standalone Bash-based exploit toolkit centered on PHP8.1.x_Exploit.sh, which orchestrates detection and exploitation of four PHP CVEs using modular helper scripts under modules/. The main script normalizes target URLs, fingerprints OS and PHP version via HTTP headers and a phpinfo.php probe, crawls homepage links/forms, enumerates likely CGI and upload endpoints, and then invokes per-CVE modules. The repository structure is simple: one main driver script, four CVE-specific Bash modules, one shared utils module, and a README. Primary exploit capability is CVE-2024-4577 against Windows PHP-CGI. The module tests two query-string injection variants, including a soft-hyphen bypass, by setting allow_url_include and auto_prepend_file=php://input and POSTing PHP code. On success it either demonstrates command execution with whoami or launches a PowerShell reverse shell to an operator-supplied IP/port. This is a real exploitation path providing RCE. A second remote capability targets CVE-2025-14177 by generating malformed JPEG files and POSTing them to discovered upload endpoints using multipart form field file. Detection looks for a marker string or long printable output in responses; exploitation repeats the upload 10 times and stores raw responses and extracted strings under a reports subdirectory, aiming to capture leaked heap data. The remaining two modules, CVE-2025-14180 and CVE-2025-14178, are effectively local/RCE-follow-on checks and crash payloads rather than pure remote exploits. Both use php -r locally when PHP CLI is present; the exploit functions POST PHP snippets to a target URL if remote code execution is already available. CVE-2025-14180 attempts to trigger a PDO PostgreSQL null dereference using DSN pgsql:host=localhost;dbname=postgres with emulated prepares enabled. CVE-2025-14178 attempts an array_merge integer overflow by allocating extremely large arrays. Both are described as potentially crashing or destabilizing the PHP process. Overall, this is an operational multi-CVE web exploitation script, not just a detector. It supports single-target and batch modes, optional GNU parallel execution, report logging, and automatic exploitation unless scan-only is specified. Fingerprintable targets include common CGI paths, common upload paths, phpinfo.php probing, php://input injection, localhost PostgreSQL access, and attacker-defined reverse-shell callback endpoints.gl1tch0x1 · Disclosed Apr 29, 2026 · bash · markdown · web · network · localOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
PHP GroupPhpapplication
FAQ

Frequently asked questions

Is CVE-2025-14180 exploited in the wild?
As of Oct 17, 2026, Mallory has no reports of CVE-2025-14180 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-14180?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2025-14180, the earliest disclosed Apr 29, 2026.
Is there a patch for CVE-2025-14180?
Upgrade PHP to 8.1.34, 8.2.30, 8.3.29, 8.4.16, 8.5.1, or a later supported release containing the fix. For Debian-packaged deployments, fixed versions include php8.2 8.2.30-1~deb12u1 for bookworm and php8.4 8.4.16-1~deb13u1 for trixie.
What products are affected by CVE-2025-14180?
PHP Group Php.
How severe is CVE-2025-14180?
CVE-2025-14180 has a CVSS v4 score of 8.2 (High) and an EPSS score of 0.70% (54th percentile) as of Oct 17, 2026.
Activity feed

Recent activity

20 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity11Community discussion across Reddit, Mastodon, and other social sources.