dbcve.org
FortimailApplication · Fortinet

CVE-2022-26114

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-06
Fix available
A fix is available. Upgrade to 7.2.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
An improper neutralization of input during web page generation vulnerability [CWE-79] in the Webmail of FortiMail before 7.2.0 may allow an unauthenticated attacker to trigger a cross-site scripting (XSS) attack via sending specially crafted mail messages.

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

A stored Cross-Site Scripting (XSS) vulnerability (CWE-79) in FortiMail Webmail before version 7.2.0 allows unauthenticated attackers to inject malicious JavaScript payloads into specially crafted email messages. When legitimate users view these emails through the webmail interface, the injected scripts execute in their browser context, potentially stealing session cookies or performing actions on behalf of the user.

MitigationUpgrade FortiMail to version 7.2.0 or later to remediate the vulnerability. Until upgrade is possible, consider disabling or restricting webmail access and implementing Content Security Policy (CSP) headers as an interim control.

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
FortimailApplication
Affected:< 7.2.0

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 FortiMail deployment
    Locate FortiMail appliances or virtual instances in your environment. Check network documentation, asset inventories, or use nmap/ping scan for FortiMail default ports (443, 80, 22) to discover active instances.
    Affected if FortiMail is deployed in the environment and is accessible on the network.
  2. Determine installed FortiMail version
    Log into the FortiMail CLI or Web UI. In the CLI, run 'get system status' to retrieve the firmware version. In the Web UI, navigate to Dashboard > System Information to view the FortiOS/FortiMail version.
    Affected if The displayed version is below 7.2.0 (for example, 7.0.x, 6.4.x, or earlier).
  3. Verify webmail interface is enabled
    In FortiMail Web UI, navigate to Domain > Domain Settings or Profile > Domain to check if Webmail access is enabled. Alternatively, check the CLI with 'get webmail service status' or review the configuration with 'show system webmail'.
    Affected if Webmail service is enabled and accessible to users or external parties.
  4. Confirm email reception from external sources
    Review mail routing policies and domain configurations to determine if the FortiMail accepts email from external/direct internet sources or from internal mail servers. Check the MTA settings and inbound mail policies.
    Affected if FortiMail receives or processes email from untrusted external sources, which could contain malicious crafted messages.

A user is affected if FortiMail with webmail enabled is running version 7.2.0 or lower and processes external email messages.

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 7.2.0 or later
Fixed in 7.2.0
Interim mitigation

Upgrade FortiMail to version 7.2.0 or later to remediate the vulnerability. Until upgrade is possible, consider disabling or restricting webmail access and implementing Content Security Policy (CSP) headers as an interim control.

Recommended fix High confidence

FortiMail 7.2.0

  1. 1. Back up current FortiMail configuration and email data
  2. 2. Download FortiMail firmware version 7.2.0 or later from Fortinet support portal (https://support.fortinet.com)
  3. 3. Access FortiMail web UI or CLI as administrator
  4. 4. Navigate to System > Firmware or use 'execute firmware upgrade' command in CLI
  5. 5. Upload and install the 7.2.0 firmware image
  6. 6. Reboot the FortiMail device when prompted
  7. 7. After reboot, verify the new firmware version is 7.2.0 or later in System > Dashboard > Status
  8. 8. Test FortiMail Webmail functionality to confirm the XSS vulnerability is remediated

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

Fix this in Fortimail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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