Threats / PHP / CVE-2019-11043
CVE-2019-11043
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
PHP FastCGI Process Manager (FPM) vulnerability
PHP FastCGI Process Manager (FPM) buffer overflow vulnerability allowing remote code execution in certain configurations. Actively exploited and used in ransomware campaigns.
Verdict
Today item, not a backlog item.
A buffer overflow in PHP FPM enables unauthenticated remote code execution on vulnerable servers. The vulnerability has been actively exploited in the wild and leveraged for ransomware deployment, posing critical risk to web infrastructure.
CISA KEV Yes · 2022-03-255Ransomware use Flagged5EPSS 0.99407 (verify live)6Exploit Weaponized · public PoC7CVSS 8.73CISA SSVC Exploitation: active · Automatable: no · Impact: total4
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
13 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-03-25), flagged for known ransomware use.
Probability (EPSS)
EPSS 0.99407 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 8.7 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N) · Affected: PHP, FastCGI Process Manager (FPM). Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-120 Buffer Copy without Size Check — weakness family: Memory safety.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 879 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious request targeting the FPM configuration to trigger a buffer overflow condition.
Business
Web application becomes compromised with arbitrary code execution at the application server level.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I establish persistence and lateral movement within the compromised server environment.
Business
Attacker gains foothold for data exfiltration, system reconnaissance, and network propagation.
3
Lateral reach — past segmentation narrative 3
Attacker
I deploy ransomware payload across the infrastructure using the compromised server as an entry point.
Business
Critical business systems are encrypted; operations halt and ransom demands are issued.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05