CI4MS has stored XSS in Pages Content Due to Missing html_purify Sanitization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.5 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

EPSS

• CVE-2026-39392: 0.25% estimated exploitation activity in the next 30 days; percentile 16.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The Pages module does not apply the htmlpurify validation rule to content fields during create and update operations, while the Blog module does. Page content is stored unsanitized in the database and rendered as raw HTML on the public frontend via echo $pageInfo-content. An authenticated admin with page-editing privileges can inject arbitrary JavaScript that executes in the browser of every public visitor viewing the page. Details The Blog module correctly applies HTMLPurifier sanitization to content fields: modules/Blog/Controllers/Blog.php:82 The Pages module omits this rule in both create and update methods: modules/Pages/Controllers/Pages.php:82 (create) modules/Pages/Controllers/Pages.php:130 (update) Content is stored directly without sanitization: modules/Pages/Controllers/Pages.php:111 (create path) modules/Pages/Controllers/Pages.php:157 (update path) On the public frontend, the content is rendered as raw HTML without escaping:…

Published by the source

8 Apr 2026, 19:15 UTC

Last modified by the source

8 Apr 2026, 19:15 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-fjpj-6qcq-6pw2

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-39392

Advisory: CI4MS has stored XSS in Pages Content Due to Missing html_purify Sanitization
IDs: CVE-2026-39392, GHSA-fjpj-6qcq-6pw2
Record: https://patchnext.com/advisories/cve-2026-39392 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ci4-cms-erp/ci4ms 0.31.4.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ci4-cms-erp/ci4ms: affected <= 0.31.3.0; fixed in 0.31.4.0

## Suggested inspection (read-only)
- Packagist ci4-cms-erp/ci4ms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on ci4-cms-erp/ci4ms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fjpj-6qcq-6pw2 (GitHub-reviewed advisory GHSA-fjpj-6qcq-6pw2 lists affected ranges: Packagist ci4-cms-erp/ci4ms >=0 <=0.31.3.0)

Commands are suggestions: review each one before running it.