dbcve.org
MailessentialsApplication · Gfi

CVE-2026-23614

MEDIUM · 5.4 CVSS v3.1 Published 2026-02-19
Fix available
A fix is available. Upgrade to 22.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the Sender Policy Framework IP Exceptions interface. An authenticated user can supply HTML/JavaScript in the ctl00$ContentPlaceHolder1$pv2$txtIPDescription parameter to /MailEssentials/pages/MailSecurity/SenderPolicyFramework.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 confidence

Stored XSS vulnerability in GFI MailEssentials AI's Sender Policy Framework IP Exceptions interface allows authenticated users to inject malicious HTML/JavaScript via the txtIPDescription parameter. The payload is stored and executed when other users view the management interface.

MitigationUpgrade to version 22.4 or later; implement input validation and output encoding on the txtIPDescription parameter to prevent script execution.

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
MailessentialsApplication
Affected:< 22.4

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm GFI MailEssentials is installed
    Locate the GFI MailEssentials installation directory or check Add/Remove Programs for 'GFI MailEssentials' entry
    Affected if GFI MailEssentials is not present on the system, the vulnerability does not apply
  2. Identify installed version number
    Check the product version through the GFI MailEssentials UI (typically in Help > About) or examine the installed binaries for version metadata
    Affected if The installed version is any version prior to 22.4 (e.g., 22.3, 22.2, older releases)
  3. Verify SPF IP Exceptions feature is accessible
    Log into the GFI MailEssentials management interface and navigate to the Sender Policy Framework (SPF) section to confirm the IP Exceptions management interface exists and is accessible
    Affected if The SPF IP Exceptions interface is not present or not accessible in the deployment
  4. Check for existing XSS indicators in txtIPDescription field
    Review any existing entries in the SPF IP Exceptions list and inspect the txtIPDescription field values for suspicious characters or encoded scripts
    Affected if Malicious payloads or encoded script tags are found stored in the txtIPDescription field values

The environment is affected if GFI MailEssentials version is below 22.4 and the SPF IP Exceptions management interface is accessible to authenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 22.4 or later
Fixed in 22.4
Interim mitigation

Upgrade to version 22.4 or later; implement input validation and output encoding on the txtIPDescription parameter to prevent script execution.

Recommended fix High confidence

GFI MailEssentials AI version 22.4

  1. 1. Obtain the GFI MailEssentials AI version 22.4 installer from the official GFI website or your licensed download portal
  2. 2. Create a full backup of the current MailEssentials configuration and database
  3. 3. Stop the GFI MailEssentials services before beginning the upgrade
  4. 4. Run the version 22.4 installer and follow the on-screen upgrade prompts
  5. 5. After installation completes, restart the GFI MailEssentials services
  6. 6. Log in to the management interface and navigate to the Sender Policy Framework page to verify the upgrade was successful
  7. 7. Confirm the ctl00$ContentPlaceHolder1$pv2$txtIPDescription parameter now properly sanitizes input

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mailessentials Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23614 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-23614 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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