FortiwebApplication · Fortinet
CVE-2021-22122
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 · uneditedAn improper neutralization of input during web page generation in FortiWeb GUI interface 6.3.0 through 6.3.7 and version before 6.2.4 may allow an unauthenticated, remote attacker to perform a reflected cross site scripting attack (XSS) by injecting malicious payload in different vulnerable API end-points.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in FortiWeb GUI versions 6.3.0-6.3.7 and before 6.2.4 allows unauthenticated remote attackers to inject malicious JavaScript payloads through vulnerable API endpoints. The attack exploits improper input validation in the web interface, causing the attacker's payload to be reflected back and executed in the victim's browser.
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.2.3>= 6.3.0, <= 6.3.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check FortiWeb GUI accessibilityVerify if the FortiWeb web interface is exposed and accessible by attempting to reach the GUI login page via HTTPS on port 443 or configured portAffected if The GUI interface is exposed and reachable (vulnerability requires GUI to be accessible)
-
Identify installed FortiWeb version via CLIRun the command 'get system status' in FortiWeb CLI or 'diagnose system version' to retrieve the exact firmware versionAffected if Version displayed is 6.3.0 through 6.3.7, or 6.2.3 or lower
-
Verify GUI version displayAccess the FortiWeb login page and check the version information typically displayed on the login screen or in the system information page after authenticationAffected if Version shown matches the affected ranges listed above
-
Check if API endpoints respondProbe common API endpoints on the FortiWeb appliance (such as /api/paths or similar) to confirm they accept unauthenticated requestsAffected if API endpoints are accessible without authentication and accept input (condition for XSS injection)
You are affected if your FortiWeb version is 6.3.0-6.3.7 or 6.2.3-and-below AND the GUI interface/API endpoints are accessible to untrusted users.
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 6.3.8, 6.2.4, or later to remediate the vulnerability. If immediate patching is not possible, consider disabling the GUI interface or restricting access to trusted IPs.
Fix this in Fortiweb
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22122 — 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-2021-22122 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