CVE-2026-27599

highpriority · track · 29EPSS 0.004 · 31 %ileEUUS
grimoire priorityP2 · Scheduled
Exploitable?
—
no known exploitation
Likely / severe?
0.37% (31st) EPSS
CVSS 7.2 · high
Is it mine?
3 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · nvd · osv

EPSS · scored 2026-10-27

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 within System Settings – Mail Settings. Several configuration fields, including Mail Server, Mail Port, Email Address, Email Password, Mail Protocol, and TLS settings, accept attacker-controlled input that is stored server-side and later rendered without proper output encoding. This issue has been patched in version 0.31.0.0.

01

cvss

Technical severity, 0–10. One row per scoring source.

9.1
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–critical · 4.7–9.1

v3.17.2highCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:Hprimary · NVD / NIST USexploitability 1.2 · impact 5.9
v3.14.7mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:Lsecondary · ENISA EU
v3.14.7mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:Lsecondary · security-advisories@github.comexploitability 1.2 · impact 3.4
v3.19.1criticalCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:Hsecondary · OSV
v3.16.6mediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:Usecondary · CVSS-BT (t0sche)
02

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Exploitation: poc · Automatable: no · Technical Impact: partialcoordinatorcisa_ssvcUS
03

weaknesses

The CWE weakness classes this flaw belongs to.

04

affected products (3)

Products and version ranges known to be affected.

05

advisories (1)

Vendor and ecosystem advisories describing this.

  • GHSA-66m2-v9v9-95c3ci4-cms-erp/ci4ms: System Settings (Mail Settings) Full Platform Compromise & Full Account Takeover for All-Roles & Privilege-Escalation via Stored DOM XSS2026-03-30ghsa · osvUS

    ## Summary ### **Vulnerability: Stored DOM XSS via System Settings – Mail Settings (Same-Page Attribute Breakout & Persistent Payload Injection)** - Stored Cross-Site Scripting via Unsanitized Mail Settings Configuration Fields ### Description The application fails to properly sanitize user-controlled input within **System Settings – Mail Settings**. Several configuration fields, including **Mail Server, Mail Port, Email Address, Email Password, Mail Protocol, and TLS settings**, accept attacker-controlled input that is stored server-side and later rendered without proper output encoding. Unlike public-facing XSS that executes on landing pages, this vulnerability executes immediately on the same settings page. The injected payload breaks out of the HTML attribute context and is interpreted by the browser when rendered, resulting in same-page DOM-based XSS. This represents different functionality and a separate vulnerability from landing-page injection. ### Example Affected Fields - Mail Server: `test` - Mail Port: `465` - Email Address: `simple@gmail.com` - Email Password: (any input) - Mail Protocol: `SMTP` - Domain: `simple@domain.com` ### Affected Functionality - System Settings – Mail Settings configuration - Same-page rendering of user-controlled input fields - DOM attribute injection within form inputs - Storage and retrieval of mail configuration values ### Attack Scenario - An attacker injects a malicious JavaScript payload into one or more Mail Settings fields. - The payload breaks out of the HTML attribute context. - The application stores and re-renders the payload without sanitization or encoding. - The payload executes immediately on the same settings page. - The script executes in the browser context of the authenticated user managing Mail Settings. ### Impact - Persistent Stored XSS - Immediate Same-Page DOM XSS execution - Execution of arbitrary JavaScript in victims’ browsers - Administrative privilege escalation - Full administrator account takeover - Full account takeover across all roles - Full compromise of the entire platform Endpoints: - `/backend/settings/` (Mail Settings) ## Steps To Reproduce (POC) 1. Navigate to System Settings -> Mail Settings 2. Insert the following XSS payload into any Mail Settings field: `test"><img src=1 onerror=alert()>" class="form-control" placeholder="Name" required>` 3. Save the settings 4. Observe that the payload breaks out of the input attribute context 5. The XSS executes immediately on the same page ## Remediation - Never use .html() or any innerHTML-style sinks for user-controlled input in PHP or JavaScript. - Apply proper **HTML encoding and input sanitization** for all configuration fields. - Enforce CSP, HttpOnly, SameSite, and Secure flags for cookies to reduce the severity of XSS and potential CSRF escalation. - Audit all other system settings fields for similar attribute injection vulnerabilities. # Ready Video POC: https://mega.nz/file/KRNhUI6Q#NGC3Bow3RlnmdU1H2bGu1BGbpfIc-awi6IlvTp08V1s

06

also known as (3)

Other names and identifiers for this entity.

07

sources

Which sources assert this record, and when.

published 2026-03-30modified 2026-06-17
08

references (5)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan