dbcve.org
FortiwebApplication · Fortinet

CVE-2020-29015

CRITICAL · 9.8 CVSS v3.1 Published 2021-01-14
Fix available
A fix is available. Upgrade to 6.2.4 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
A blind SQL injection in the user interface of FortiWeb 6.3.0 through 6.3.7 and version before 6.2.4 may allow an unauthenticated, remote attacker to execute arbitrary SQL queries or commands by sending a request with a crafted Authorization header containing a malicious SQL statement.

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 blind SQL injection vulnerability exists in FortiWeb's user interface that allows an unauthenticated remote attacker to execute arbitrary SQL queries or commands by sending a crafted Authorization header containing malicious SQL statements. The vulnerability affects versions 6.3.0 through 6.3.7 and versions prior to 6.2.4.

MitigationUpgrade FortiWeb to version 6.3.8 or later, or version 6.2.4 or later, to remediate this vulnerability. As an interim measure, restrict network access to the FortiWeb management interface.

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
FortiwebApplication
Affected:< 6.2.4>= 6.3.0, <= 6.3.7

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 FortiWeb installation
    Run 'get system status' on the FortiWeb CLI or check the web UI footer for the product name and version
    Affected if The product is not FortiWeb (this CVE is FortiWeb-specific)
  2. Determine FortiWeb version
    On the CLI, run 'get system status' and locate the 'Version' field. In the web UI, the version appears in the footer of all pages.
    Affected if The installed version is < 6.2.4 OR >= 6.3.0 AND <= 6.3.7
  3. Verify management interface accessibility
    Confirm network access to the FortiWeb management interface (HTTPS on port 443 by default) from untrusted networks. Check firewall rules or run 'show system interface' to list management-enabled ports.
    Affected if The management interface is exposed to untrusted networks (the vulnerability is exploitable remotely without authentication)

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.2.4 or later
Fixed in 6.2.4
Interim mitigation

Upgrade FortiWeb to version 6.3.8 or later, or version 6.2.4 or later, to remediate this vulnerability. As an interim measure, restrict network access to the FortiWeb management interface.

Recommended fix High confidence

FortiWeb 6.2.4 or later (for < 6.2.4); FortiWeb 6.3.8 or later (for 6.3.0-6.3.7)

  1. 1. Identify the current FortiWeb version by accessing the Web UI or running 'get system status' in the CLI
  2. 2. If running FortiWeb < 6.2.4, plan upgrade to version 6.2.4 or later
  3. 3. If running FortiWeb >= 6.3.0 and <= 6.3.7, plan upgrade to version 6.3.8 or later
  4. 4. Download the appropriate firmware upgrade from Fortinet customer support portal or FortiGuard
  5. 5. Back up the current FortiWeb configuration before upgrading
  6. 6. Upload and install the new firmware via Web UI (System > Firmware) or CLI ('execute firmware upgrade')
  7. 7. After upgrade, verify the system is operational and confirm the new version is installed
Caveat Review FortiWeb release notes for any configuration or feature changes between your current version and the target version before upgrading

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,950
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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