dbcve.org
MailessentialsApplication · Gfi

CVE-2026-23613

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 URI DNS Blocklist configuration page. An authenticated user can supply HTML/JavaScript in the ctl00$ContentPlaceHolder1$pv1$TXB_URIs parameter to /MailEssentials/pages/MailSecurity/uridnsblocklist.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

GFI MailEssentials AI versions prior to 22.4 contain a stored XSS vulnerability in the URI DNS Blocklist configuration page (uridnsblocklist.aspx). An authenticated user can inject malicious HTML/JavaScript via the ctl00$ContentPlaceHolder1$pv1$TXB_URIs parameter, which is stored and executed in the browsers of other logged-in users viewing the page.

MitigationUpgrade to GFI MailEssentials AI version 22.4 or later. As an interim measure, restrict administrative access to the uridnsblocklist.aspx page to trusted personnel only until the update is applied.

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. Identify installed GFI MailEssentials AI version
    Locate the installed version of GFI MailEssentials AI in the product UI, registry, or installation directory and note the full version number
    Affected if The version is lower than 22.4 (e.g., 22.3, 22.2, earlier versions)
  2. Verify uridnsblocklist.aspx page exists
    Check if the file uridnsblocklist.aspx exists in the GFI MailEssentials web interface directory (typically under the MailEssentials or web folder in the installation path)
    Affected if The file exists and the product version is below 22.4
  3. Confirm administrative access is enabled
    Determine if the web interface allows authenticated administrative access - verify that the GFI MailEssentials administration portal is accessible with valid credentials
    Affected if Administrative authentication is enabled and the product version is below 22.4
  4. Inspect URI DNS Blocklist configuration for anomalous content
    Access the URI DNS Blocklist configuration page (uridnsblocklist.aspx) as an administrator and examine the URI list field (ctl00$ContentPlaceHolder1$pv1$TXB_URIs) for any unexpected or encoded values that resemble HTML or JavaScript
    Affected if The page displays unexpected HTML tags, script elements, or encoded characters in the URI list field that were not personally entered

A user is affected if GFI MailEssentials AI version is below 22.4 and the uridnsblocklist.aspx page is accessible to authenticated administrators who may have stored malicious scripts in the URI Blocklist configuration.

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. As an interim measure, restrict administrative access to the uridnsblocklist.aspx page to trusted personnel only until the update is applied.

Recommended fix High confidence

22.4

  1. Backup the current GFI MailEssentials configuration and database
  2. Download GFI MailEssentials AI version 22.4 from the official GFI download portal
  3. Stop the GFI MailEssentials services before upgrading
  4. Run the installer for version 22.4 and follow the on-screen upgrade instructions
  5. Restart the GFI MailEssentials services after the upgrade completes
  6. Log into the management interface and navigate to the URI DNS Blocklist configuration page (uridnsblocklist.aspx)
  7. Verify the XSS payload is no longer executable and the interface renders input safely
  8. Confirm all other MailEssentials functionality is operating normally

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

Fix this in Mailessentials Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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