CVE-2023-38490

MEDIUMNVD 6.86.8
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.8 under NVD CVSS v3. EPSS exploit probability: 20.4%, top 4% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 2%CVSS: 6.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
6.8
EG Score
6.8(medium)
EPSS
71.7%
KEV
Not listed

Published

July 27, 2023

Last Modified

November 21, 2024

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
getkirby/cms3.9.0 ... 3.9.6-rc.1 (12 versions)3.9.6

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 46× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:26 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:08 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-08 15:13 UTCEPSS rescore
  6. 2026-07-07 13:44 UTCEPSS rescore
  7. 2026-07-06 16:26 UTCEPSS rescore
  8. 2026-07-06 16:26 UTCEPSS rescore
  9. 2026-07-06 02:21 UTCEPSS rescore
  10. 2026-07-05 02:29 UTCEPSS rescore
  11. 2026-07-04 06:29 UTCEPSS rescore
  12. 2026-07-02 16:59 UTCEPSS rescore
  13. 2026-07-01 15:04 UTCEPSS rescore
  14. 2026-06-30 23:21 UTCEPSS rescore
  15. 2026-06-30 23:21 UTCEPSS rescore
  16. 2026-06-28 14:06 UTCEPSS rescore
  17. 2026-06-28 14:06 UTCEPSS rescore
  18. 2026-06-28 04:55 UTCEPSS rescore
  19. 2026-06-28 04:55 UTCEPSS rescore
  20. 2026-06-27 14:34 UTCOSV refresh
  21. 2026-06-27 03:07 UTCEPSS rescore
  22. 2026-06-27 03:07 UTCEPSS rescore
  23. 2026-06-25 13:48 UTCEPSS rescore
  24. 2026-06-25 13:48 UTCEPSS rescore
  25. 2026-06-24 14:04 UTCEPSS rescore
Show 56 more
  1. 2026-06-24 14:03 UTCEPSS rescore
  2. 2026-06-23 21:31 UTCEPSS rescore
  3. 2026-06-23 21:31 UTCEPSS rescore
  4. 2026-06-21 14:55 UTCEPSS rescore
  5. 2026-06-21 14:55 UTCEPSS rescore
  6. 2026-06-21 01:58 UTCEPSS rescore
  7. 2026-06-21 01:58 UTCEPSS rescore
  8. 2026-06-19 19:24 UTCEPSS rescore
  9. 2026-06-19 19:24 UTCEPSS rescore
  10. 2026-06-18 17:51 UTCEPSS rescore
  11. 2026-06-18 17:51 UTCEPSS rescore
  12. 2026-06-17 17:51 UTCEPSS rescore
  13. 2026-06-17 17:51 UTCEPSS rescore
  14. 2026-06-16 17:51 UTCEPSS rescore
  15. 2026-06-16 17:51 UTCEPSS rescore
  16. 2026-06-15 17:47 UTCEPSS rescore
  17. 2026-06-14 23:16 UTCEPSS rescore
  18. 2026-06-13 22:59 UTCEPSS rescore
  19. 2026-06-13 22:59 UTCEPSS rescore
  20. 2026-06-12 23:10 UTCEPSS rescore
  21. 2026-06-12 23:10 UTCEPSS rescore
  22. 2026-06-11 13:59 UTCEPSS rescore
  23. 2026-06-11 13:59 UTCEPSS rescore
  24. 2026-06-10 22:17 UTCEPSS rescore
  25. 2026-06-10 13:21 UTCEPSS rescore
  26. 2026-06-10 01:17 UTCOSV refresh
  27. 2026-06-07 15:23 UTCEPSS rescore
  28. 2026-06-07 15:23 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-06 13:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-05 22:46 UTCEPSS rescore
  33. 2026-06-05 06:09 UTCEPSS rescore
  34. 2026-06-05 06:09 UTCEPSS rescore
  35. 2026-06-04 13:11 UTCEPSS rescore
  36. 2026-06-04 13:11 UTCEPSS rescore
  37. 2026-06-02 20:12 UTCEPSS rescore
  38. 2026-06-02 20:12 UTCEPSS rescore
  39. 2026-06-02 20:12 UTCEPSS rescore
  40. 2026-06-01 13:51 UTCEPSS rescore
  41. 2026-06-01 13:51 UTCEPSS rescore
  42. 2026-05-31 22:30 UTCEPSS rescore
  43. 2026-05-31 22:29 UTCEPSS rescore
  44. 2026-05-31 22:29 UTCEPSS rescore
  45. 2026-05-31 00:15 UTCEPSS rescore
  46. 2026-05-31 00:15 UTCEPSS rescore
  47. 2026-05-29 13:43 UTCEPSS rescore
  48. 2026-05-29 13:43 UTCEPSS rescore
  49. 2026-05-28 13:43 UTCEPSS rescore
  50. 2026-05-28 13:43 UTCEPSS rescore
  51. 2026-05-27 13:39 UTCEPSS rescore
  52. 2026-05-26 07:18 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-24 20:32 UTCEG score recompute
  56. 2026-05-24 16:52 UTCEPSS rescore

Frequently asked(5)

What is CVE-2023-38490?
CVE-2023-38490 is a medium vulnerability published on July 27, 2023. 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…
When was CVE-2023-38490 disclosed?
CVE-2023-38490 was first published in the National Vulnerability Database on July 27, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-38490 actively exploited?
CVE-2023-38490 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-38490?
CVE-2023-38490 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2023-38490?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-38490, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-38490

Explore →

Is Your Infrastructure Affected by CVE-2023-38490?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.