CVE intelligence and bounded remediation
CVE-2023-38490 — Kirby is a content management system
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.…
- Severity
- Critical
- CVSS
- 10 (3.1)
- Published
- 2023-07-27
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-611, CWE-776
Affected products
- getkirby / kirby
Matched remediation archetype
XML external entity and unsafe XML processing
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory XML parsers used by APIs, file imports, office or image formats, identity protocols, feeds, and background jobs.
- Determine whether document type declarations, external entities, XInclude, schemas, or network resolvers are enabled.
- Map parser filesystem and network access and the sensitivity of documents it processes.
Remediate safely
- Configure each parser to reject document type declarations and disable external entity, XInclude, and network resolution features.
- Prefer a data format or hardened parser that does not support external resolution, and apply input size and depth limits.
- Update affected XML libraries and centralize secure parser construction so callers cannot silently override it.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.