CVE-2019-9020

This vulnerability is in PHP, the software many websites use to run server-side code. If someone sends specially malformed XML-RPC messages, PHP may read memory it shouldn’t, which can crash the server or (in the worst case) lead to compromise. It’s like a door lock that sometimes breaks when someone jams it with the wrong shape of key.

This matters to you if your small business runs or hosts web applications using the PHP versions listed as vulnerable (before 5.6.40, 7.1.26, 7.2.14, or 7.3.1). It’s especially relevant if your app exposes XML-RPC functionality to the internet, because the bug is reachable through malformed XML-RPC input. Risk is present only if the vulnerable PHP code path is reachable (for example, if XML-RPC is enabled and an attacker can send requests to it).

Attackers have public exploit code available, and exploitation likelihood is rising, which makes this a timely risk for exposed services. Because it’s tied to invalid memory access, it can cause immediate instability and potentially enable serious impact in vulnerable setups, so you should treat it as urgent (but not “wait-and-see” for every business).

1. Confirm exposure

   • Identify all servers/environments where PHP is running (production, staging if it’s internet-exposed, and any internal web apps.
   • Record the exact PHP version.
   • Check whether XML-RPC is enabled/used (for example, whether your application exposes XML-RPC endpoints and/or loads the xmlrpc-related functionality).

2. Determine if you are affected

   • Affected PHP versions are:
     • PHP before 5.6.40
     • PHP 7.x before 7.1.26
     • PHP 7.2.x before 7.2.14
     • PHP 7.3.x before 7.3.1
   • If your version is within those ranges and XML-RPC input can reach xmlrpc_decode(), you should treat it as affected.

3. Apply the fix (target versions)

   • Upgrade to the fixed PHP version for your branch:
     • Upgrade to 5.6.40 or later
     • Upgrade to 7.1.26 or later
     • Upgrade to 7.2.14 or later
     • Upgrade to 7.3.1 or later
   • If you are on Debian and upgrading is supported via packages, follow the distribution’s update to the fixed PHP release.

4. Workaround if you cannot upgrade immediately

   • Disable/remove XML-RPC functionality if your business app doesn’t require it.
   • Block external network access to any XML-RPC endpoints until the fixed PHP version is installed.

5. After upgrading

   • Re-test XML-RPC features (if used) to confirm normal operation.
   • Watch logs for crashes or abnormal errors around XML-RPC requests.

6. Timeline guidance

   • No CISA KEV listing was found in the provided findings, so follow your normal security change window—but given public exploits and rising likelihood, aim to complete remediation quickly.

CVE-2019-9020 affects PHP’s XML-RPC decoding path (xmlrpc_decode(), linked to ext/xmlrpc/libxmlrpc/xml_element.c / xml_elem_parse_buf). The weakness is a memory-safety bug (CWE-125 and CWE-416) caused by invalid input leading to invalid memory access (heap out of bounds read or read after free). Public exploit code is available (weaponization indicates “2 known” public exploits), and press attention is rising; KEV is not listed. EPSS is reported as 10.1% with a rising trend, but public exploit availability and rising attention increase practical risk. KEV was not provided as a confirming exploitation signal in the findings, so urgency is based on the availability of public exploits and rising likelihood rather than a KEV-confirmed event.