Categories
CVE-2026-45270 high CVSS 8.7

Cross-Site Scripting (XSS) in ci4-cms-erp/ci4ms (CVE-2026-45270)

Summary

Cross-site scripting in ci4-cms-erp/ci4ms (CVE-2026-45270). Confidential information can be exposed externally. Exploitable via Pages. Mitigation: upgrade to 0.31.9.0 or later.

Original description

The description as published by the source.

CI4MS is a CodeIgniter 4-based content management system skeleton. Prior to version 0.31.9.0, the Pages backend module registers the html_purify validation rule on language-keyed page content but persists the raw, un-purified POST value into the database. The public renderer for pages (Home::index() → app/Views/templates/default/pages.php) emits $pageInfo->content without esc(), yielding stored XSS that fires for every public visitor of the affected page — including administrators. Because pages may be promoted to the site home page, the payload can be served at / and reach every visitor of the site. Version 0.31.9.0 patches the issue.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-45270 has been found in ci4-cms-erp/ci4ms.
Attackers can target a specific entry point like Pages over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade ci4-cms-erp/ci4ms to 0.31.9.0 or later.
If unsure, ask your IT team or search "ci4-cms-erp/ci4ms CVE-2026-45270" on the vendor's site.

CVE-2026-45270 (ci4-cms-erp/ci4ms) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: Pages / html_purify / pages_langs.content / blog_langs.content
Patched: 0.31.9.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in ci4-cms-erp/ci4ms. Attackers reach the vulnerable code path via Pages.

📍 Affected scope

Check the vendor advisory for the affected versions of ci4-cms-erp/ci4ms. Attack surface: Pages / html_purify / pages_langs.content / blog_langs.content.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 0.31.9.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ci4-cms-erp/ci4ms' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'ci4-cms-erp/ci4ms' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で ci4-cms-erp/ci4ms を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade ci4-cms-erp/ci4ms to 0.31.9.0

    ステージング環境で 0.31.9.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer ci4-cms-erp/ci4ms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.31.9.0"}]}]
Packagist ci4-cms-erp/ci4ms
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.31.9.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details