dbcve.org
FortimailApplication · Fortinet

CVE-2021-24007

CRITICAL · 9.8 CVSS v3.1 Published 2021-07-09
Fix available
A fix is available. Upgrade to 6.0.11 / 6.2.7 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Multiple improper neutralization of special elements of SQL commands vulnerabilities in FortiMail before 6.4.4 may allow a non-authenticated attacker to execute unauthorized code or commands via specifically crafted HTTP requests.

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

Multiple SQL injection vulnerabilities in FortiMail before version 6.4.4 allow unauthenticated attackers to execute unauthorized code or commands via specifically crafted HTTP requests. The improper neutralization of special elements in SQL commands enables attackers to manipulate database queries.

MitigationUpgrade FortiMail to version 6.4.4 or later. If immediate patching is not possible, restrict HTTP access to the management interface using network segmentation or firewall rules to limit exposure to untrusted networks.

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:<= 5.4.12>= 5.6.1, < 6.0.11>= 6.2.0, < 6.2.7>= 6.4.0, < 6.4.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 version via CLI
    Log into the FortiMail CLI and run the command: get system status. This displays the firmware version installed.
    Affected if The version displayed is <= 5.4.12, or >= 5.6.1 and < 6.0.11, or >= 6.2.0 and < 6.2.7, or >= 6.4.0 and < 6.4.4
  2. Identify FortiMail version via web UI
    Access the FortiMail web login page and check the login page footer or navigate to System > Settings to view the firmware version.
    Affected if The version displayed is <= 5.4.12, or >= 5.6.1 and < 6.0.11, or >= 6.2.0 and < 6.2.7, or >= 6.4.0 and < 6.4.4
  3. Verify HTTP management interface is enabled
    In the FortiMail web UI, navigate to System > Network > Interface. Check if the mgmt or any interface has HTTP (port 80) or HTTP service enabled for the management access settings.
    Affected if HTTP access is enabled on any interface, making the SQL injection exploitable over HTTP requests
  4. Check network exposure of management interface
    Review firewall or network segmentation rules to determine if the FortiMail management interface (port 80/443) is accessible from untrusted networks or the internet.
    Affected if The management interface is exposed to untrusted networks, allowing remote attackers to send malicious HTTP requests

A user is affected if their FortiMail version falls within the vulnerable ranges AND the HTTP management interface is network-accessible to untrusted 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 6.0.11 / 6.2.7 / 6.4.4 or later
Fixed in 6.0.116.2.76.4.4
Interim mitigation

Upgrade FortiMail to version 6.4.4 or later. If immediate patching is not possible, restrict HTTP access to the management interface using network segmentation or firewall rules to limit exposure to untrusted networks.

Recommended fix High confidence

FortiMail 6.4.4 or later

  1. Identify the current FortiMail version via the web UI or CLI (diagnose system version)
  2. Review the FortiMail 6.4.4 release notes for any known upgrade considerations
  3. Ensure adequate backup of FortiMail configuration and mail data
  4. Download FortiMail firmware version 6.4.4 or later from Fortinet support portal
  5. Upload the firmware via FortiMail web UI (System > Maintenance > Firmware) or CLI (execute restore image)
  6. Verify the firmware upgrade was successful and services are operational
  7. Confirm the version shows 6.4.4 or later after upgrade
Caveat Review release notes for any configuration or feature changes between your current version and 6.4.4

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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