External risk intelligence

CI4MS Stored Cross-Site Scripting Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.4)

CVE-2026-34989

The vulnerable product is a content management system (CMS). CMS platforms are commonly deployed as public-facing web applications to serve content to internet users, making their web interfaces and user profile management features readily reachable from the public internet in typical deployment scenarios.

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

A critical vulnerability exists in the CI4MS content management system that allows an attacker to inject malicious code into a user's profile name. This code can then be executed across various application views when displayed, potentially compromising user sessions or data. The issue is related to improper sanitization of user-supplied input, specifically within the profile name field.

  • Malicious code can run in the system.
  • Profile name input is not safely handled.
  • Confirm if this system is in use.

Attack Path

How an attacker could exploit the issue

An attacker with a low-privilege account can inject malicious JavaScript into their profile name. This script is stored by the system and later displayed on various parts of the application without proper security checks, allowing the attacker to execute arbitrary code within the victim's browser.

  • Requires authenticated access.
  • Triggered by updating profile name.
  • Risk of arbitrary code execution.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to inject malicious JavaScript into a user's profile name. When this profile information is displayed elsewhere in the application, the injected script may execute, potentially impacting the user's session or the application's view.

  • User profile names.
  • Malicious script injected into profile.
  • Stored XSS affecting application views.

Operational Fix

Recommended remediation, mitigation, and detection steps

The CI4MS application owners and platform teams are likely responsible for addressing this stored cross-site scripting vulnerability. The first practical step involves identifying all instances of CI4MS, confirming their exposure and criticality, and then engaging the appropriate teams for remediation planning.

  • Application and platform teams own.
  • Verify CI4MS instances and reachability.
  • Plan and execute updates.

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 the CI4MS software?

CI4MS is a modular content management system built on the CodeIgniter 4 framework. Developers use it as a foundation to build websites that require built-in features like role-based access control, content organization, and theme management. Because it serves as a CMS, it is designed to handle user accounts and display dynamic content across a web interface.

What does CVE-2026-34989 mean for security?

This vulnerability is classified as Improper Neutralization of Input During Web Page Generation, commonly known as Stored Cross-Site Scripting (XSS). It means the application fails to scrub malicious code from user-provided data. When the system stores this tainted data and displays it to other users, their browsers treat the code as legitimate parts of the webpage, potentially leading to unauthorized script execution.

How is this XSS vulnerability triggered?

An attacker triggers this flaw by inserting a malicious JavaScript payload into their own profile name field within the application. Once saved, the application unknowingly stores this script. The bug does not trigger if a user simply views their own profile; rather, it activates whenever the application renders that stored profile name in other views or pages where the script can run in another user's browser session.

Why should I care about this CI4MS vulnerability?

According to Halo Surface Signal, CI4MS is typically deployed as a public-facing web application. Since the software is designed to serve content to internet users, the profile management features affected by this bug are often accessible from the open web. This means an attacker does not necessarily need deep internal network access to reach the vulnerable input field.

How do I respond to this vulnerability?

Your first step is to perform an inventory of your environment to identify any running instances of CI4MS. Once you have a list, check the installed version against the secure release, which is 31.0.0.0 or later. If you are running an older version, coordinate with your development or platform teams to plan and apply the update to eliminate the input sanitization flaw.

References