dbcve.org
FortiwebApplication · Fortinet

CVE-2022-29059

HIGH · 7.2 CVSS v3.1 Published 2025-03-14
Fix available
A fix is available. Upgrade to 7.0.2 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
An improper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability [CWE-89] in FortiWeb version 7.0.1 and below, 6.4.2 and below, 6.3.20 and below, 6.2.7 and below may allow a privileged attacker to execute SQL commands over the log database via specifically crafted strings parameters.

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

SQL injection vulnerability in FortiWeb's log database allows a privileged attacker to execute arbitrary SQL commands via crafted string parameters. The flaw exists in versions 7.0.1 and below, 6.4.2 and below, 6.3.20 and below, and 6.2.7 and below, stemming from improper neutralization of special elements in SQL queries.

MitigationUpgrade FortiWeb to version 7.0.2, 6.4.3, 6.3.21, or 6.2.8 or later per vendor advisories. Limit administrative access and monitor for suspicious log database queries as interim controls.

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.3, <= 6.2.7>= 6.3.0, <= 6.3.18>= 6.4.0, <= 6.4.2>= 7.0.0, < 7.0.2

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 version
    Run CLI command: get system status or check System > Settings in the web UI to view the firmware version
    Affected if Version is 6.2.3-6.2.7, 6.3.0-6.3.18, 6.4.0-6.4.2, or 7.0.0-7.0.1
  2. Confirm log database feature is configured
    Check if FortiWeb log database is enabled via CLI: get log {type} or navigate to Log > Log Config in the web UI
    Affected if Log database feature is active and receiving logs
  3. Review administrative access logs
    Audit privileged user accounts with access to log database via CLI: diagnose system admin list or check Log Access settings for recent logins
    Affected if Multiple or unauthorized accounts have privileged administrative access to the log database
  4. Inspect log database queries
    Search FortiWeb logs for suspicious SQL syntax patterns such as UNION, SELECT, DROP, or unexpected semicolons in log search queries
    Affected if Unusual SQL-like commands appear in log search or audit logs

You are affected if your FortiWeb version falls within 6.2.3-6.2.7, 6.3.0-6.3.18, 6.4.0-6.4.2, or 7.0.0-7.0.1 and the log database feature is accessible to privileged 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 7.0.2 or later
Fixed in 7.0.2
Interim mitigation

Upgrade FortiWeb to version 7.0.2, 6.4.3, 6.3.21, or 6.2.8 or later per vendor advisories. Limit administrative access and monitor for suspicious log database queries as interim controls.

Recommended fix High confidence

FortiWeb 7.0.2 or later (7.0.x branch recommended; 6.4.x and earlier branches are End of Life)

  1. 1. Identify the current FortiWeb version via Web UI (System > Status) or CLI: 'get system status'
  2. 2. Based on your current version branch, plan upgrade path: For 7.0.x, upgrade to 7.0.2 or later; for 6.4.x, upgrade to 7.0.2 or later (6.4.x is EOL); for 6.3.x, upgrade to 7.0.2 or later (6.3.x is EOL); for 6.2.x, upgrade to 7.0.2 or later (6.2.x is EOL)
  3. 3. Backup FortiWeb configuration via Web UI (System > Maintenance > Backup & Restore) or CLI: 'execute backup full-config'
  4. 4. Download the firmware upgrade from Fortinet Customer Support portal (https://support.fortinet.com)
  5. 5. Upload and install the firmware via Web UI (System > Maintenance > Firmware) or CLI: 'execute system firmware upgrade'
  6. 6. After upgrade, verify version: 'get system status' to confirm running fixed version
  7. 7. Test that FortiWeb functionality (especially logging and SQL-related features) operates normally
Caveat Upgrading across major version branches (e.g., 6.x to 7.0.x) may require configuration review; always test in staging first

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

Fix this in Fortiweb 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-2022-29059 — 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-29059 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