GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Spam Keyword Checking (Subject) conditions interface. An authenticated user can supply HTML/JavaScript in the ctl00$ContentPlaceHolder1$pvSubject$TXB_SubjectCondition parameter to /MailEssentials/pages/MailSecurity/ASKeywordChecking.aspx, which is stored and later rendered in the management interface, allowing script execution in the context of a logged-in user.
Security readout for executives and security teams
Plain-English summary
CVE-2026-23618 lets an authenticated GFI MailEssentials AI user store malicious web content in an anti-spam subject condition. When another logged-in administrator later views the management interface, script may run in that user’s browser. This is not described as unauthenticated remote compromise, but it can affect admin-session confidentiality and integrity.
Executive priority
Treat this as a moderate-priority patch and access-control issue. It is most urgent where many users can administer mail security settings or where the management console is broadly reachable. Patch during the next maintenance window unless local exposure or suspicious rule changes raise urgency.
Technical view
Stored XSS exists in GFI MailEssentials AI before 22.4 in the Spam Keyword Checking subject condition interface. The vulnerable field is saved and later rendered in /MailEssentials/pages/MailSecurity/ASKeywordChecking.aspx. CVSS 3.1 is 5.4, CWE-79, with network access, low attack complexity, low privileges, required user interaction, changed scope, and low confidentiality/integrity impact.
Likely exposure
Organizations running GFI MailEssentials AI before 22.4 are most relevant. Exposure depends on authenticated access to the MailEssentials management interface and use of Spam Keyword Checking subject conditions. The provided data does not identify anonymous exposure or other affected GFI products.
Exploitation context
The source bundle marks CISA KEV as false and provides no cited evidence of active exploitation. The vulnerability requires an authenticated user to store content and a logged-in user to later view the affected management interface.
Researcher notes
The key uncertainty is real-world exploitation: sources identify the flaw and patch reference, but not exploitation in the wild. Validate versioning carefully because the structured affected entry is sparse, while the title and description state versions before 22.4 are affected.
Mitigation direction
Upgrade GFI MailEssentials AI to 22.4 or later, following GFI release guidance.
Restrict MailEssentials administrative access to trusted users and networks.
Review account permissions for users allowed to change anti-spam keyword rules.
Monitor vendor advisories for any additional mitigation or hardening instructions.
Validation and detection
Inventory all GFI MailEssentials AI installations and confirm exact versions.
Check whether any instance is earlier than version 22.4.
Review Spam Keyword Checking subject conditions for unexpected HTML or script content.
Inspect admin audit logs for recent suspicious anti-spam rule changes.
After upgrade, verify saved subject conditions render as inert text.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.