10.0
CRITICAL
CVE-2023-38490
Kirby XML External Entity Injection Vulnerability
Description

Kirby is a content management system. A vulnerability in versions prior to 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6 only affects Kirby sites that use the `Xml` data handler (e.g. `Data::decode($string, 'xml')`) or the `Xml::parse()` method in site or plugin code. The Kirby core does not use any of the affected methods. XML External Entities (XXE) is a little used feature in the XML markup language that allows to include data from external files in an XML structure. If the name of the external file can be controlled by an attacker, this becomes a vulnerability that can be abused for various system impacts like the disclosure of internal or confidential data that is stored on the server (arbitrary file disclosure) or to perform network requests on behalf of the server (server-side request forgery, SSRF). Kirby's `Xml::parse()` method used PHP's `LIBXML_NOENT` constant, which enabled the processing of XML external entities during the parsing operation. The `Xml::parse()` method is used in the `Xml` data handler (e.g. `Data::decode($string, 'xml')`). Both the vulnerable method and the data handler are not used in the Kirby core. However they may be used in site or plugin code, e.g. to parse RSS feeds or other XML files. If those files are of an external origin (e.g. uploaded by a user or retrieved from an external URL), attackers may be able to include an external entity in the XML file that will then be processed in the parsing process. Kirby sites that don't use XML parsing in site or plugin code are *not* affected. The problem has been patched in Kirby 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6. In all of the mentioned releases, the maintainers have removed the `LIBXML_NOENT` constant as processing of external entities is out of scope of the parsing logic. This protects all uses of the method against the described vulnerability.

INFO

Published Date :

July 27, 2023, 3:15 p.m.

Last Modified :

Aug. 3, 2023, 1:31 p.m.

Remotely Exploitable :

Yes !

Impact Score :

5.8

Exploitability Score :

3.9
Public PoC/Exploit Available at Github

CVE-2023-38490 has a 1 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

Affected Products

The following products are affected by CVE-2023-38490 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Getkirby kirby
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2023-38490.

URL Resource
https://github.com/getkirby/kirby/commit/277b05662d2b67386f0a0f18323cf68b30e86387 Patch Third Party Advisory
https://github.com/getkirby/kirby/releases/tag/3.5.8.3 Third Party Advisory
https://github.com/getkirby/kirby/releases/tag/3.6.6.3 Third Party Advisory
https://github.com/getkirby/kirby/releases/tag/3.7.5.2 Third Party Advisory
https://github.com/getkirby/kirby/releases/tag/3.8.4.1 Third Party Advisory
https://github.com/getkirby/kirby/releases/tag/3.9.6 Third Party Advisory
https://github.com/getkirby/kirby/security/advisories/GHSA-q386-w6fg-gmgp Third Party Advisory

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Kirby < 3.9.6 XML External Entity exploit

cve exploit kirby kirby-cms xxe cve-2023-38490

Dockerfile PHP

Updated: 1 year, 2 months ago
0 stars 2 fork 2 watcher
Born at : July 28, 2023, 9:19 a.m. This repo has been linked 1 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2023-38490 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2023-38490 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by [email protected]

    May. 14, 2024

    Action Type Old Value New Value
  • Initial Analysis by [email protected]

    Aug. 03, 2023

    Action Type Old Value New Value
    Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
    Changed Reference Type https://github.com/getkirby/kirby/commit/277b05662d2b67386f0a0f18323cf68b30e86387 No Types Assigned https://github.com/getkirby/kirby/commit/277b05662d2b67386f0a0f18323cf68b30e86387 Patch, Third Party Advisory
    Changed Reference Type https://github.com/getkirby/kirby/releases/tag/3.5.8.3 No Types Assigned https://github.com/getkirby/kirby/releases/tag/3.5.8.3 Third Party Advisory
    Changed Reference Type https://github.com/getkirby/kirby/releases/tag/3.6.6.3 No Types Assigned https://github.com/getkirby/kirby/releases/tag/3.6.6.3 Third Party Advisory
    Changed Reference Type https://github.com/getkirby/kirby/releases/tag/3.7.5.2 No Types Assigned https://github.com/getkirby/kirby/releases/tag/3.7.5.2 Third Party Advisory
    Changed Reference Type https://github.com/getkirby/kirby/releases/tag/3.8.4.1 No Types Assigned https://github.com/getkirby/kirby/releases/tag/3.8.4.1 Third Party Advisory
    Changed Reference Type https://github.com/getkirby/kirby/releases/tag/3.9.6 No Types Assigned https://github.com/getkirby/kirby/releases/tag/3.9.6 Third Party Advisory
    Changed Reference Type https://github.com/getkirby/kirby/security/advisories/GHSA-q386-w6fg-gmgp No Types Assigned https://github.com/getkirby/kirby/security/advisories/GHSA-q386-w6fg-gmgp Third Party Advisory
    Added CPE Configuration OR *cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:* versions from (including) 3.5.0 up to (excluding) 3.5.8.3 *cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:* versions from (including) 3.6.0 up to (excluding) 3.6.6.3 *cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:* versions from (including) 3.7.0 up to (excluding) 3.7.5.2 *cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:* versions from (including) 3.8.0 up to (excluding) 3.8.4.1 *cpe:2.3:a:getkirby:kirby:*:*:*:*:*:*:*:* versions from (including) 3.9.0 up to (excluding) 3.9.6
  • CVE Modified by [email protected]

    Jul. 27, 2023

    Action Type Old Value New Value
    Changed Description Kirby is a content management system. A vulnerability in versions prior to 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6 only affects Kirby sites that use the `Xml` data handler (e.g. `Data::decode($string, 'xml')`) or the `Xml::parse()` method in site or plugin code. The Kirby core does not use any of the affected methods. XML External Entities (XXE) is a little used feature in the XML markup language that allows to include data from external files in an XML structure. If the name of the external file can be controlled by an attacker, this becomes a vulnerability that can be abused for various system impacts like the disclosure of internal or confidential data that is stored on the server (arbitrary file disclosure) or to perform network requests on behalf of the server (server-side request forgery, SSRF). Kirby's `Xml::parse()` method used PHP's `LIBXML_NOENT` constant, which enabled the processing of XML external entities during the parsing operation. The `Xml::parse()` method is used in the `Xml` data handler (e.g. `Data::decode($string, 'xml')`). Both the vulnerable method and the data handler are not used in the Kirby core. However they may be used in site or plugin code, e.g. to parse RSS feeds or other XML files. If those files are of an external origin (e.g. uploaded by a user or retrieved from an external URL), attackers may be able to include an external entity in the XML file that will then be processed in the parsing process. Kirby sites that don't use XML parsing in site or plugin code are *not* affected. The problem has been patched in Kirby 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and Kirby 3.9.6. In all of the mentioned releases, the maintainers have removed the `LIBXML_NOENT` constant as processing of external entities is out of scope of the parsing logic. This protects all uses of the method against the described vulnerability. Kirby is a content management system. A vulnerability in versions prior to 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6 only affects Kirby sites that use the `Xml` data handler (e.g. `Data::decode($string, 'xml')`) or the `Xml::parse()` method in site or plugin code. The Kirby core does not use any of the affected methods. XML External Entities (XXE) is a little used feature in the XML markup language that allows to include data from external files in an XML structure. If the name of the external file can be controlled by an attacker, this becomes a vulnerability that can be abused for various system impacts like the disclosure of internal or confidential data that is stored on the server (arbitrary file disclosure) or to perform network requests on behalf of the server (server-side request forgery, SSRF). Kirby's `Xml::parse()` method used PHP's `LIBXML_NOENT` constant, which enabled the processing of XML external entities during the parsing operation. The `Xml::parse()` method is used in the `Xml` data handler (e.g. `Data::decode($string, 'xml')`). Both the vulnerable method and the data handler are not used in the Kirby core. However they may be used in site or plugin code, e.g. to parse RSS feeds or other XML files. If those files are of an external origin (e.g. uploaded by a user or retrieved from an external URL), attackers may be able to include an external entity in the XML file that will then be processed in the parsing process. Kirby sites that don't use XML parsing in site or plugin code are *not* affected. The problem has been patched in Kirby 3.5.8.3, 3.6.6.3, 3.7.5.2, 3.8.4.1, and 3.9.6. In all of the mentioned releases, the maintainers have removed the `LIBXML_NOENT` constant as processing of external entities is out of scope of the parsing logic. This protects all uses of the method against the described vulnerability.
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2023-38490 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2023-38490 weaknesses.

Exploit Prediction

EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.

0.34 }} 0.04%

score

0.72008

percentile

CVSS31 - Vulnerability Scoring System
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality
Integrity
Availability