dbcve.org
MailessentialsApplication · Gfi

CVE-2026-23610

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 POP2Exchange configuration endpoint. An authenticated user can supply HTML/JavaScript in the POP3 server login field within the JSON \"popServers\" payload to /MailEssentials/pages/MailSecurity/POP2Exchange.aspx/Save, 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

GFI MailEssentials AI versions prior to 22.4 contain a stored cross-site scripting vulnerability in the POP2Exchange configuration endpoint. An authenticated user can inject malicious HTML/JavaScript code into the POP3 server login field within the JSON 'popServers' payload sent to /MailEssentials/pages/MailSecurity/POP2Exchange.aspx/Save. This payload is stored in the database and executed in the context of other logged-in users when the management interface renders the stored data.

MitigationUpgrade to GFI MailEssentials AI version 22.4 or later which addresses this vulnerability. As a temporary measure, implement input validation and output encoding on the POP2Exchange configuration endpoint.

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 AI installation
    Locate the GFI MailEssentials installation directory, typically found in C:\Program Files\GFI\MailEssentials or C:\Program Files (x86)\GFI\MailEssentials. Check for MailEssentials.exe or verify through Windows Programs and Features.
    Affected if The software is installed and the version is below 22.4
  2. Determine installed version
    Right-click MailEssentials.exe, select Properties, and view the File Version, or check the version through the management interface under Help > About. Compare this version number to the affected range (versions prior to 22.4).
    Affected if The installed version is lower than 22.4 (for example, 22.3, 22.2, 21.x, etc.)
  3. Verify POP2Exchange feature usage
    Access the GFI MailEssentials management console via web browser (typically http://localhost:8081 or https://localhost). Navigate to Mail Security > POP2Exchange. Check if any POP3 accounts are configured.
    Affected if POP2Exchange is enabled and configured with POP3 server accounts
  4. Inspect stored POP3 server configuration
    Navigate to the POP2Exchange configuration page in the management interface. Examine the POP3 server login fields for any unexpected characters, scripts, or HTML tags. Alternatively, query the backend database (typically SQL Server) for the popServers table or equivalent configuration storage.
    Affected if The POP3 server login field contains unsanitized HTML, JavaScript tags, or suspicious encoded content that would execute when viewed
  5. Review user access logs
    Check GFI MailEssentials event logs or IIS logs for POST requests to /MailEssentials/pages/MailSecurity/POP2Exchange.aspx/Save with unusual payload patterns in the popServers JSON field.
    Affected if Recent Save operations contain popServers payloads with HTML script tags, javascript: URIs, or event handler attributes

You are affected if GFI MailEssentials AI is installed with a version lower than 22.4 AND the POP2Exchange feature is configured with potentially malicious POP3 server login credentials stored in the database.

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 GFI MailEssentials AI version 22.4 or later which addresses this vulnerability. As a temporary measure, implement input validation and output encoding on the POP2Exchange configuration endpoint.

Recommended fix High confidence

22.4

  1. Upgrade GFI MailEssentials AI to version 22.4 or later
  2. After upgrading, verify the POP2Exchange configuration endpoint (/MailEssentials/pages/MailSecurity/POP2Exchange.aspx) no longer reflects unescaped HTML/JavaScript in the POP3 server login field
  3. Confirm the management interface properly sanitizes and encodes the popServers data upon display

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 / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-23610 — 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-23610 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