How to Fix CVE-2026-34563: ci4ms (Bundle Sibling)

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

CVE-2026-34563 is a sibling vulnerability in the same Ci4-cms-erp ci4ms advisory bundle as CVE-2026-34559. The same patched build closes every CVE in the bundle, so the remediation procedure for CVE-2026-34563 matches the primary write-up.

What is different about CVE-2026-34563?

CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to version 0.31.0.0, the application fails to properly sanitize user-controlled input when handling backup uploads and processing backup metadata. An attacker can inject a malicious JavaScript payload into the backup filename via the uploaded xss.sql, which uses SQL functionality to insert the XSS payload server-side.

Impact is consistent with the bundle: execution of attacker-controlled JavaScript in a victim's browser. The patched build closes every code path in the advisory in one update.

How to fix CVE-2026-34563

Apply the patched build per the primary write-up: How to Fix CVE-2026-34559.

For a quick check, confirm the running version of ci4ms:

# Confirm the installed version via your package manager
dpkg -l | grep -i ci4ms   # Debian/Ubuntu
rpm -qa | grep -i ci4ms   # RHEL/CentOS/Rocky

Frequently asked questions

Is CVE-2026-34563 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

How severe is CVE-2026-34563?

CVSS rates it 9.1 (Critical). Use that score to set your patch priority alongside the other items in your queue.

Do I have to take ci4ms offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

What if my vulnerability scanner still flags CVE-2026-34563 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

References

• Official vendor advisory: https://github.com/ci4-cms-erp/ci4ms/security/advisories/GHSA-85m8-g393-jcxf
• NVD entry: https://nvd.nist.gov/vuln/detail/CVE-2026-34563
• CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
• Primary write-up: How to Fix CVE-2026-34559

*Written by Sai Kiran Pandrala. Last verified 2026-05-25. Part of the Ci4-cms-erp ci4ms advisory bundle. Full procedure at how-to-fix-cve-2026-34559.*