External risk intelligence

CI4MS Blind Cross-Site Scripting in Logs Interface

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-34560

The vulnerable component is a Content Management System (CMS), which is commonly deployed as an internet-facing web application. Since the vulnerability resides in the administrative logs interface, it is reachable via the web-based management surface that administrators access to monitor and manage the public-facing site.

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 vulnerability in a content management system that could allow an attacker to inject malicious code into application logs, which then executes when an administrator views those logs. While the attack requires an administrator to access the logs, the potential impact could involve unauthorized access or data manipulation. The primary concern at this time is to confirm if this specific system is in use and, if so, to understand its exposure.

  • Malicious code in logs executes when viewed.
  • Attackers don't see immediate results.
  • Confirm system relevance and exposure.

Attack Path

How an attacker could exploit the issue

An attacker can target this vulnerability by injecting malicious code into application logs, likely through a feature where user input is logged. This code remains dormant until an administrator views the logs, at which point it executes in the administrator's browser, potentially leading to significant compromise.

  • Requires authenticated access.
  • Stored input executed when logs viewed.
  • Leads to high impact on administrator.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could impact the integrity of application logs when an attacker injects a stored Cross-Site Scripting (XSS) payload into logged data. The payload is then executed when an administrator views the logs page, potentially leading to unauthorized actions or information disclosure within the administrator's session.

  • Application logs could be compromised.
  • Malicious scripts execute when logs are viewed.
  • Sensitive information or actions may be exposed.

Operational Fix

Recommended remediation, mitigation, and detection steps

CI4MS application owners and infrastructure teams are likely responsible for addressing this blind cross-site scripting (XSS) vulnerability. The first practical step is to identify all instances of CI4MS, confirm their exposure and business criticality, and then work with the accountable owners to plan remediation, prioritizing systems that are internet-facing or handle sensitive data.

  • Application owners and infrastructure teams.
  • Verify CI4MS deployment and exposure.
  • Plan and coordinate remediation efforts.

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 provides developers and site administrators with a pre-configured architecture for managing web content, including built-in Role-Based Access Control and theming capabilities. It is typically used to deploy and maintain dynamic, data-driven websites.

What does CVE-2026-34560 mean for security?

This vulnerability is classified as CWE-79, or Cross-Site Scripting (XSS). It occurs because the application fails to properly clean user-supplied data before showing it in the logs. Because the malicious code is stored within the log files and triggers later, it is specifically referred to as a Blind XSS attack.

How does an attacker trigger this log-based vulnerability?

An attacker triggers this by submitting a malicious script into the application where input is tracked by logs. It does not trigger upon simple submission; rather, it remains dormant in the system logs. Execution only occurs when an authenticated administrator opens the logs interface in their browser to review the data.

Is my instance of CI4MS at risk?

According to Halo Surface Signal, this software is commonly deployed as an internet-facing application, making it a likely target. Because the vulnerability exists within the management interface that administrators use, any CI4MS deployment—especially those accessible via the internet—should be treated as needing verification of its security posture.

What is the first step to fix this issue?

The primary step is to identify all deployed versions of CI4MS within your environment to determine which systems are running software older than version 0.31.0.0. Once you have located these instances, you should prioritize updating to the latest version, which includes the necessary output encoding fixes to prevent unauthorized script execution.

References