Quick answers
- Is CVE-2026-39392 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39392 being exploited in the wild.
- How severe is CVE-2026-39392?
- Medium severity, with a CVSS score of 5.5, published 8 April 2026.
- Which products and versions are affected?
- ci4-cms-erp/ci4ms (Packagist) ECOSYSTEM:introduced=0,fixed=0.31.4.0.
- Is there a fix for CVE-2026-39392?
- Yes. ci4-cms-erp/ci4ms (Packagist): upgrade to 0.31.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39392 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39392?
- Check whether you run ci4-cms-erp/ci4ms (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- ci4-cms-erp/ci4ms (Packagist): upgrade to 0.31.4.0 or later
composer require ci4-cms-erp/ci4ms:^0.31.4.0
Technical details
A stored cross-site scripting (XSS) vulnerability exists in the Pages module of CI4MS due to the omission of the 'html_purify' validation rule in the create and update methods of the Pages controller. While the Blog module correctly sanitizes input, the Pages module stores raw HTML content in the database and subsequently renders it on the frontend using unescaped output (echo $pageInfo->content). An attacker with administrative privileges can exploit this to inject arbitrary JavaScript. Because the script executes in the context of other users' sessions (including other admins and public visitors), the vulnerability results in a scope change (S:C). The issue is resolved in version 0.31.4.0 by applying the proper validation rules.
Affected products
- ci4-cms-erp CI4MS < 0.31.4.0
Identifiers
- CVE-2026-39392
- GHSA-fjpj-6qcq-6pw2
Timeline
- 2026-04-07: advisory: GitHub Security Advisory published
- 2026-04-08: disclosed: CVE published to NVD
- 2026-04-08: patched: Vulnerability fixed in version 0.31.4.0