FortiwebApplication · Fortinet
CVE-2022-39951
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 · uneditedA improper neutralization of special elements used in an os command ('os command injection') in Fortinet FortiWeb version 7.0.0 through 7.0.2, FortiWeb version 6.3.6 through 6.3.20, FortiWeb 6.4 all versions allows 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 confidenceOS command injection vulnerability in FortiWeb's HTTP request parsing allows attackers to inject and execute arbitrary operating system commands via specially crafted HTTP requests. The flaw exists in versions 7.0.0-7.0.2, 6.3.6-6.3.20, and all 6.4 versions.
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
>= 6.3.6, <= 6.3.20>= 6.4.0, <= 6.4.2>= 7.0.0, <= 7.0.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FortiWeb is deployed in your environmentIdentify whether Fortinet FortiWeb web application firewall is installed and running in your infrastructure. This may be a hardware appliance, virtual machine, or cloud instance.Affected if FortiWeb is not present in your environment, you are not affected.
-
Retrieve the FortiWeb version numberAccess the FortiWeb CLI and run the command to display system information, typically 'get system status' or 'fnsysctl get system status'. Alternatively, log into the FortiWeb GUI and navigate to System > Status to view the firmware version.Affected if Unable to determine the version means further investigation is needed.
-
Compare your version against the affected rangesCheck if your installed version falls within any of these ranges: 6.3.6 through 6.3.20, 6.4.0 through 6.4.2, or 7.0.0 through 7.0.2.Affected if Your version is within one of these ranges, meaning you are potentially affected by CVE-2022-39951.
-
Verify HTTP request parsing is enabledConfirm that FortiWeb is configured to handle and parse HTTP traffic. This is typically the default operational mode for FortiWeb as a WAF, but verify via the GUI under Server Infrastructure or through CLI commands like 'get server-info system' or 'show system interface'.Affected if HTTP/HTTPS traffic parsing is disabled and FortiWeb is not actively processing requests, the exploit surface may be reduced.
You are affected if FortiWeb is deployed and the installed version falls within 6.3.6-6.3.20, 6.4.0-6.4.2, or 7.0.0-7.0.2 while HTTP request parsing is active.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade FortiWeb to version 7.0.3 or later (for 7.x) or 6.3.21 or later (for 6.3.x); version 6.4 is end-of-life and requires upgrade to a supported version.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39951 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-39951 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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