CVE-2026-23611
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 IP Blocklist management page. An authenticated user can supply HTML/JavaScript in the ctl00$ContentPlaceHolder1$pv1$txtIPDescription parameter to /MailEssentials/pages/MailSecurity/ipblocklist.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 prior to 22.4 contain a stored XSS vulnerability in the IP Blocklist management page (ipblocklist.aspx). An authenticated attacker can inject malicious HTML/JavaScript via the txtIPDescription parameter, which gets stored in the database and executed in the browsers of other administrative users who view the IP Blocklist 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.
-
Identify if GFI MailEssentials is installedCheck for the presence of GFI MailEssentials in your environment. Common installation paths include C:\Program Files\GFI\MailEssentials or check Windows Programs and Features for GFI MailEssentials.Affected if GFI MailEssentials is found installed on the system.
-
Determine the installed versionLocate the version information. Check the Windows registry under HKLM\SOFTWARE\GFI\MailEssentials\Version, or look for version info in the GFI MailEssentials installation directory, typically in an About or version file.Affected if The installed version is lower than 22.4 (e.g., 22.3, 22.2, earlier versions).
-
Verify access to the IP Blocklist management interfaceConfirm that the ipblocklist.aspx page is accessible. This is typically found in the GFI MailEssentials web configuration interface, often under the Anti-Spam or Configuration section.Affected if The IP Blocklist management page (ipblocklist.aspx) is accessible via the web interface.
-
Check if administrative authentication is availableVerify that you have or can obtain administrative credentials for the GFI MailEssentials web interface, as the vulnerability requires an authenticated attacker.Affected if Administrative credentials exist or can be obtained for the GFI MailEssentials console.
A user is affected if GFI MailEssentials version is below 22.4 AND they have administrative access to the IP Blocklist management interface where the txtIPDescription parameter can be manipulated.
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 version 22.4 or later. Additionally, implement proper input validation and output encoding for the txtIPDescription field to prevent XSS.
22.4
- Identify the current version of GFI MailEssentials AI installed in your environment
- Review the GFI MailEssentials AI 22.4 release notes and upgrade documentation
- Create a complete backup of the current MailEssentials configuration
- Upgrade GFI MailEssentials AI to version 22.4 or later
- Verify the upgrade was successful and the IP Blocklist management page functions correctly
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-23611 — 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-23611 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