External risk intelligence

CI4MS Stored Cross-Site Scripting Vulnerability in Categories

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-34567

The vulnerable product is a CMS (Content Management System) skeleton designed for production use. CMS platforms are commonly deployed as internet-facing web applications to manage content, making the categories and blog post features, where the vulnerability exists, reachable by web users in typical deployments.

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 has been identified in the CI4MS content management system. This issue could allow an attacker to inject malicious scripts into blog post content, which may then execute within a user's browser when they view the content. While the direct business impact requires further assessment of your specific deployment, the nature of the vulnerability warrants attention to confirm relevance.

  • Allows malicious scripts in blog posts.
  • Matters if content is shared or viewed.
  • Confirm exposure and relevance to operations.

Attack Path

How an attacker could exploit the issue

An attacker with low-privilege access can inject malicious JavaScript into the content of blog post categories. This script is stored on the server and later executed when those categories are viewed, potentially leading to a critical compromise.

  • Low-privilege authenticated access required.
  • Injecting script into category content.
  • Stored cross-site scripting (XSS) risk.

Live Threat

Current exploitation, exposure, and threat context

A stored cross-site scripting vulnerability in CI4MS could allow an authenticated attacker to inject malicious JavaScript into blog post categories. This script could execute when other users view these categories, potentially impacting their browsing session.

  • Blog post category content at risk.
  • Malicious JavaScript injected via category edits.
  • Compromised user sessions and data exposure.

Operational Fix

Recommended remediation, mitigation, and detection steps

The CI4MS CMS skeleton's stored XSS vulnerability requires coordination between application owners and infrastructure teams. The first practical step is to identify all instances of CI4MS, determine their reachability and business criticality, confirm accountable owners, and then prioritize remediation efforts.

  • Application owners should investigate.
  • Verify reachability and business criticality.
  • Plan coordinated remediation actions.

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 skeleton built on CodeIgniter 4. It provides a production-ready foundation for websites, including features like Role-Based Access Control (RBAC) and theme management. Developers use it to organize content, such as blog posts and categories, while managing how different users interact with the site's administrative and public-facing functions.

How does CVE-2026-34567 cause a security weakness?

This vulnerability is classified as CWE-79, or stored cross-site scripting (XSS). It occurs because the application fails to sanitize text input within the blog post categories section. When an attacker saves malicious JavaScript there, the server stores it. When other users view those categories later, their browsers mistakenly treat that stored text as executable code, allowing the script to run in their session.

Do I need special access to trigger this vulnerability?

Yes. This bug requires low-privilege authenticated access to the system. An attacker must be able to log in and reach the specific blog category editing tools to inject the malicious script. Simply browsing the public-facing side of the website or viewing existing content without editing permissions will not trigger the vulnerability.

Is my CI4MS installation at risk?

According to Halo Surface Signal, this vulnerability is likely relevant to you if your instance is internet-facing. Because CI4MS is a CMS designed for production, it is commonly deployed where categories and blog posts are reachable by web users. If your installation is accessible via the internet, the potential for malicious scripts to affect users viewing your content is significantly higher.

When should I take action to fix this?

You should prioritize this as soon as possible by identifying all running instances of CI4MS in your environment. Confirm which versions are below 0.31.0.0 and coordinate with your team to apply the update provided by the maintainers. Prioritizing these systems is essential because the vulnerability involves stored scripts that could impact any user who accesses the affected content.

References