Home/CVE/In PHP versions 7.2.x below 7.2.26, 7.3.x below 7.3.13 and 7.4.0 on Windows, PHP link() function accepts filenames with
CVE

CVE-2019-110442

In PHP versions 7.2.x below 7.2.26, 7.3.x below 7.3.13 and 7.4.0 on Windows, PHP link() function accepts filenames with

In PHP versions 7.2.x below 7.2.26, 7.3.x below 7.3.13 and 7.4.0 on Windows, PHP link() function accepts filenames with embedded \0 byte and treats them as terminating at that byte. This could lead to security vulnerabilities, e.g. in applications checking paths that the code is allowed to access.

LOW · CVSS 3.7 EPSS 0.05124
EPSS exploitation odds5.12% · top 8%
Schedule remediation
  • EPSS percentile: top 8% of all CVEs by exploitation likelihood
  • Public exploit or PoC is available
Look this up elsewhere - one-click external pivots
How to read a CVE - triage first, then detect and patch
This page is every public fact about CVE-2019-11044, cross-linked. Its job is to answer one question fast - does this need my attention now? - and then hand you the two things you do about it. Here is how an analyst reads it.
Triage: should I act now? Four signals, and they are not interchangeable:
CVSSseverity - how bad it is IF exploited, 0-10. A high CVSS alone is not urgency; a flaw can be a perfect 10 and never actually be attacked. EPSSprobability - a model’s estimate of the chance it is exploited in the next 30 days, 0-1. This is the “will it actually happen” signal. CISA KEVconfirmed - it is being exploited in the wild right now. The strongest signal on the page; KEV beats any score. Weaponisedavailability - public exploits / PoCs, and especially Metasploit modules rated Excellent / Great. Reliable, packaged exploit code means low-skill attackers can use it today.
How they combine: KEV, or a dependable Metasploit module, means patch now regardless of CVSS. High CVSS + low EPSS + no exploit is real but not an emergency - schedule it. Low CVSS but KEV-listed still gets patched now. The verdict above already weighed these for you; this is how it got there.
Then what - two workflows:
Detectwhen you cannot patch today, follow this CVE to the ATT&CK techniques it enables, then Build a SIEM detection (the green button) - author a rule, test it in Atomic, deploy it. That buys visibility while the patch waits. PatchAffected products / packages tell you if you are exposed; Fixed versions by distribution and Vendor advisories give the exact version that closes it.
Reading order for the panels below: verdict + badges, then Public exploits / Metasploit (is it weaponised), then ATT&CK techniques + Sigma / IDS rules (can I detect it), then Affected products / packages + Fixed versions (am I exposed, what patches it), then Threat actors / IOCs (who uses it), then Scoring & timeline / references (the evidence).

Exploitation evidence

1 of 7 sources
Corroboration score 8/100 · emerging. This counts how many independent sources have exploitation evidence, and separates two different things: confirmed in-the-wild use (CISA KEV, Microsoft MSRC, ransomware activity) from exploit / PoC availability (Metasploit, ExploitDB, Nuclei, public PoCs). A template or PoC existing means an attack is possible and easy - it is not, on its own, proof the CVE is being exploited in the wild.
Exploit / PoC available
public PoC

Exploitation momentum

496 days of EPSS
stable
Exploitation pressure is steady. This reads the direction and speed of EPSS over time, which can move before EPSS itself peaks or before CISA lists it.
Window

Severity & exploitation scoring

View on NVD →
CVSS base score
3.7
LOWCVSS v3.1 · [email protected]
EPSS exploitation probability
5.12%
Top 8%odds of exploitation in the next 30 days
CVSS metric silhouette
VectorComplexityPrivilegesInteractionScopeConfidentialityIntegrityAvailability
shape grows toward worst-case
SSVC triage
No SSVC vulnrichment for this CVE. CISA's Vulnrichment program scores newer CVEs (~2024 onwards) plus selected older critical ones. Use the EPSS probability + KEV status to triage instead.
CVSS vector breakdown
Exploitability - how they get in
Attack Vector
Network Adjacent Local Physical
Attack Complexity
Low High
Privileges Required
None Low High
User Interaction
None Required
Scope
Unchanged Changed
Impact - what breaks
Confidentiality
None Low High
Integrity
None Low High
Availability
None Low High
VECTORCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N
Lifecycle
  1. 23 Dec 2019Published to NVD
  2. 17 Jun 2026Last modified
Every entry is a recorded date - NVD publish/modify, CISA KEV add, public exploit disclosure. No inferred events.
Attack path
Full kill chain

Public Exploits & PoCs

2
These PoC and exploit links come from public sources and are not verified to be safe or functional. Review the code before running anything, and treat unverified entries as untrusted. Signed-in users mark whether it works, rate 1-10, and can report malware with a required reason that becomes a public comment.
poc Public PoC (nvd-reference) date unknown
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -
poc bugs.php.net · bug.php?id=78862 bugs.php.net
Vote & rate
Report or claim
⚠ Report this PoC

Becomes a public comment attributed as First L. (never full last name). Don't include private info. Rate-limited: 5/hour.

Works? no reports yet
Rating -

ATT&CK techniques

1

Techniques this CVE enables. Pills with a solid outline are high confidence - named directly in ATT&CK or Nuclei, or human-curated by CTID; the rest are inferred from the weakness type using MITRE's CVE Mapping Methodology and the CWE → CAPEC chain. Broad, generic-weakness guesses are filtered out. A small marks a technique that N independent sources agree on.

▤ Build a SIEM detection for these techniques

Weakness Classification

Affected Products & Versions

5
php>= 7.2.0 and <= 7.2.26
php>= 7.3.0 and <= 7.3.13
phpall versions
📦

Fixed versions by distribution

52
The package version that resolves this CVE on each Linux distribution, from the vendor’s published security data. fixed in shows a patched version exists; open means the package is listed as affected with no fix yet.
suse sle15apache2-mod_php7 open
suse sle15php7 open
suse sle15php7-bcmath open
suse sle15php7-bz2 open
suse sle15php7-calendar open
suse sle15php7-ctype open
suse sle15php7-curl open
suse sle15php7-dba open
suse sle15php7-devel open
suse sle15php7-dom open
suse sle15php7-enchant open
suse sle15php7-exif open
suse sle15php7-fastcgi open
suse sle15php7-fileinfo open
suse sle15php7-fpm open
suse sle15php7-ftp open
suse sle15php7-gd open
suse sle15php7-gettext open
suse sle15php7-gmp open
suse sle15php7-iconv open
suse sle15php7-intl open
suse sle15php7-json open
suse sle15php7-ldap open
suse sle15php7-mbstring open
suse sle15php7-mysql open
suse sle15php7-odbc open
suse sle15php7-opcache open
suse sle15php7-openssl open
suse sle15php7-pcntl open
suse sle15php7-pdo open
suse sle15php7-pear open
suse sle15php7-pear-Archive_Tar open
suse sle15php7-pgsql open
suse sle15php7-phar open
suse sle15php7-posix open
suse sle15php7-shmop open
suse sle15php7-snmp open
suse sle15php7-soap open
suse sle15php7-sockets open
suse sle15php7-sodium open
suse sle15php7-sqlite open
suse sle15php7-sysvmsg open
suse sle15php7-sysvsem open
suse sle15php7-sysvshm open
suse sle15php7-tokenizer open
suse sle15php7-wddx open
suse sle15php7-xmlreader open
suse sle15php7-xmlrpc open
suse sle15php7-xmlwriter open
suse sle15php7-xsl open
suse sle15php7-zip open
suse sle15php7-zlib open

Vendor Advisories

1
cisa-csafcisa-csaf-csaf_files-OT-white-2026-icsa-26-027-02