External risk intelligence

CI4MS Stored DOM-based XSS in Navigation Menus

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-34565

The vulnerability affects a Content Management System (CMS) that explicitly renders navigation menus on public-facing web pages. Since these public menus are a primary component of the software's functionality, the vulnerable surface is commonly exposed to the internet as part of a standard website deployment.

Cross-site Scripting

Ci4 Cms Erp Ci4ms

before 0.31.0.0

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in CI4MS, a content management system, that could allow attackers to inject malicious code into administrative dashboards and public-facing navigation menus. The flaw arises from improper handling of user input when adding posts to navigation menus, potentially leading to stored cross-site scripting attacks. The main concern is confirming relevance and exposure to your systems.

  • Malicious code can be injected into menus.
  • Critical vulnerability impacts public-facing content.
  • Confirm relevance and assess potential exposure.

Attack Path

How an attacker could exploit the issue

An attacker with low-privileged access can target the Menu Management feature to inject malicious scripts. By adding posts with specially crafted data to navigation menus, the attacker can cause these scripts to be stored and later executed when administrative dashboards or public navigation menus are rendered, leading to stored DOM-based XSS.

  • Requires authenticated access.
  • Injecting data into navigation menus.
  • Stored DOM-based cross-site scripting.

Live Threat

Current exploitation, exposure, and threat context

When users interact with the menu management functionality, specially crafted post data could be stored and later rendered unsafely in administrative dashboards and public navigation menus, potentially leading to stored DOM-based cross-site scripting.

  • Administrative dashboard content and public navigation menus.
  • Unsanitized user input stored and rendered unsafely.
  • Unauthorized code execution within user browsers.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-world action for this vulnerability likely falls to the application owners or platform teams responsible for the CI4MS deployment. The first practical step is to inventory all instances of the affected CMS, confirm their reachability and business criticality, and then identify the accountable owner for each instance before planning remediation.

  • Application owners should manage remediation.
  • Verify affected deployments and owner accountability.
  • Plan risk-based remediation during maintenance.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is CI4MS?

CI4MS is a modular content management system built on the CodeIgniter 4 framework. It is used by organizations to manage web content, providing built-in features like role-based access control (RBAC), theme management, and menu configuration to organize posts and pages for public audiences.

What does this CVE-2026-34565 vulnerability mean?

This vulnerability is a Stored DOM-based Cross-Site Scripting (XSS) flaw, categorized as CWE-79. It occurs because the software fails to sanitize data when posts are added to menus. Consequently, malicious scripts can be saved by the system and later executed in the browsers of anyone viewing the compromised navigation menus or administrative dashboards.

How is this vulnerability triggered?

An attacker triggers this by using a low-privileged account to access the Menu Management feature. They insert specially crafted script code into post data that is then added to a menu. Simply navigating the site or viewing benign content does not trigger the bug; the script must be explicitly injected into the menu data path.

Do I need to worry if my CI4MS instance is internal?

Halo Surface Signal indicates that because this vulnerability impacts public-facing navigation menus, the risk is highest for instances accessible over the internet. While internal-only deployments reduce the scope of potential external attackers, the risk remains if unauthorized users have access to the administrative menu management functions.

What should I do if I use CI4MS?

First, identify all active CI4MS deployments in your environment and confirm which are running versions prior to 0.31.0.0. Once localized, coordinate with the responsible application owners to verify their exposure and prioritize updating to version 0.31.0.0, which contains the necessary security patch.

References