CVE-2026-23609
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 Perimeter SMTP Servers configuration page. An authenticated user can supply HTML/JavaScript in the ctl00$ContentPlaceHolder1$pv3$txtDescription parameter to /MailEssentials/pages/MailSecurity/PerimeterSMTPServers.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 have a stored XSS vulnerability in the Perimeter SMTP Servers configuration page. The txtDescription parameter in PerimeterSMTPServers.aspx accepts HTML/JavaScript payloads that are stored and rendered without proper sanitization, executing in the context of any user who views 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.
-
Identify installed GFI MailEssentials versionCheck the product version in the GFI MailEssentials administration interface or installed programs list. This is typically found in the product's About or System Status page.Affected if The installed version is any version before 22.4 (e.g., 22.3, 22.2, earlier releases).
-
Locate Perimeter SMTP Servers configuration pageNavigate to the PerimeterSMTPServers.aspx page in the GFI MailEssentials web interface. This is typically found under the SMTP Server or Perimeter settings section of the administration console.Affected if The page is accessible in the environment (indicating the vulnerable component is present).
-
Inspect txtDescription field contentExamine the PerimeterSMTPServers.aspx page source or use browser developer tools to view the HTML rendered for the txtDescription field. Look for any stored HTML or JavaScript content in the description parameter.Affected if The txtDescription field contains unencoded HTML tags (e.g., <script>, <img>, <iframe>) or JavaScript code that executes when the page loads.
-
Verify XSS vulnerability through observationReview the rendered output of the txtDescription field. If the application renders raw HTML/JavaScript from user input without encoding (e.g., showing <script>alert(1)</script> as executable code rather than as escaped text), the vulnerability is present.Affected if HTML or JavaScript entered in the txtDescription field is rendered and executed in the browser without being entity-encoded (e.g., <script> displays as literal text vs <script> which executes).
The environment is affected if GFI MailEssentials AI version is below 22.4 AND the PerimeterSMTPServers.aspx page is accessible with the txtDescription field rendering unencoded HTML or JavaScript content.
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
Implement HTML entity encoding for all user-supplied input in the txtDescription field before storage and upon rendering. Apply input validation to reject or sanitize potentially malicious characters. Consider implementing a content security policy (CSP) as defense-in-depth.
22.4
- 1. Verify current GFI MailEssentials version by navigating to the management interface or checking the installed version.
- 2. Download GFI MailEssentials version 22.4 or later from the official GFI download portal or vendor repository.
- 3. Before upgrading, backup the current configuration and any custom settings.
- 4. Install version 22.4 following the vendor's standard upgrade procedure.
- 5. After upgrade, verify the Perimeter SMTP Servers configuration page now properly sanitizes input in the txtDescription field.
- 6. Confirm the vulnerability is remediated by attempting to inject benign HTML/JavaScript in the affected parameter and verifying it is not executed.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23609 — 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-23609 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