CVE-2026-23606
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Advanced Content Filtering rule creation workflow. An authenticated user can supply HTML/JavaScript in the ctl00$ContentPlaceHolder1$pv1$txtRuleName parameter to /MailEssentials/pages/MailSecurity/advancedfiltering.aspx, which is stored and later rendered in the management interface, allowing script execution in the context of a logged-in user.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceGFI MailEssentials AI versions before 22.4 contain a stored XSS vulnerability in the Advanced Content Filtering rule creation page (advancedfiltering.aspx). An authenticated attacker can inject malicious HTML/JavaScript into the txtRuleName parameter, which persists and executes when administrators view the filtering rules in the management interface.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 22.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm GFI MailEssentials AI is installedCheck for GFI MailEssentials installation by looking in Program Files for GFI folder, or check Windows Services for 'GFI MailEssentials' serviceAffected if GFI MailEssentials AI is not installed on the system
-
Check installed version against affected rangeOpen the GFI MailEssentials management interface or check Add/Remove Programs for the version number. Compare to the affected range: versions before 22.4 are vulnerableAffected if The installed version is lower than 22.4 (e.g., 22.3, 22.2, earlier versions)
-
Verify Advanced Content Filtering feature accessAttempt to access the advancedfiltering.aspx page in the GFI MailEssentials web management interface (typically found under Filtering > Content Filtering > Advanced)Affected if The advancedfiltering.aspx page is accessible without error
-
Check for existing content filtering rulesIn the GFI MailEssentials management console, navigate to Content Filtering and view any existing rules. Look specifically at the rule names listedAffected if Any filtering rules exist in the system (the stored XSS payload would be embedded in the rule name field)
-
Inspect rule name parameters for injection markersIf you have access to the backend configuration files or database, examine the stored rule names in the filtering rules configuration. Look for unusual characters or patterns in rule names that could indicate injectionAffected if Rule names contain unexpected HTML tags, script elements, or JavaScript event handlers
A user is affected if GFI MailEssentials AI version below 22.4 is installed AND the Advanced Content Filtering feature is accessible, with any rules containing potentially malicious txtRuleName values that could execute when viewed in the management interface.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped22.4
Upgrade to GFI MailEssentials AI version 22.4 or later, which contains the patch for this stored XSS vulnerability.
GFI MailEssentials AI version 22.4
- Ensure you have a complete backup of your GFI MailEssentials configuration and database before proceeding
- Log in to the GFI MailEssentials server with administrator credentials
- Download GFI MailEssentials AI version 22.4 from the official GFI download portal or your licensed download area
- Run the installer and follow the on-screen upgrade wizard prompts
- Complete the upgrade and verify all services start successfully
- Log in to the management interface and navigate to Advanced Content Filtering to confirm the new version is running
- Test creating a new filtering rule to verify the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data