dbcve.org
FortiwebApplication · Fortinet

CVE-2022-43955

MEDIUM · 6.1 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 6.3.22 / 7.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 input during web page generation [CWE-79] in the FortiWeb web interface 7.0.0 through 7.0.3, 6.3.0 through 6.3.21, 6.4 all versions, 6.2 all versions, 6.1 all versions and 6.0 all versions may allow an unauthenticated and remote attacker to perform a reflected cross site scripting attack (XSS) via injecting malicious payload in log entries used to build report.

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 reflected cross-site scripting (XSS) vulnerability in FortiWeb web interface allows unauthenticated remote attackers to inject malicious JavaScript payloads into log entries. These entries are later rendered in reports without proper sanitization, enabling the attacker's script to execute in the context of legitimate users viewing those reports.

MitigationUpgrade FortiWeb to a patched version beyond 7.0.3, 6.3.21, or the latest available version that addresses this vulnerability. Until patched, limit access to reporting features and monitor for suspicious log entries.

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.0.0, <= 6.2.7>= 6.3.0, < 6.3.22>= 6.4.0, <= 6.4.2>= 7.0.0, < 7.0.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiWeb version
    Log into the FortiWeb CLI and run the command 'get system status' or check the web interface login page footer for the firmware version number
    Affected if The installed version falls within any of these ranges: 6.0.0 through 6.2.7, 6.3.0 through 6.3.21, 6.4.0 through 6.4.2, or 7.0.0 through 7.0.3
  2. Verify web interface is enabled
    In the FortiWeb CLI, run 'show system interface' or check the web UI service status to confirm the administrative web interface is accessible
    Affected if The web interface is exposed and reachable on HTTP/HTTPS ports
  3. Confirm logging is enabled
    In the web UI, navigate to Logd > Log Config > Log Settings, or run 'show log_fortiweb' in CLI to verify event logging is turned on
    Affected if Logging is enabled, which is typically the default configuration and necessary for the malicious log entries to be stored
  4. Check report access
    Navigate to Logd > Reports in the web UI or run 'show log_fortiweb-report' to see if report generation is configured and accessible to users
    Affected if Report viewing functionality is available to users who would open log entries in reports

You are affected if your FortiWeb version is within the vulnerable ranges listed AND the web interface with logging and reporting features is enabled and accessible.

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.3.22 / 7.0.4 or later
Fixed in 6.3.227.0.4
Interim mitigation

Upgrade FortiWeb to a patched version beyond 7.0.3, 6.3.21, or the latest available version that addresses this vulnerability. Until patched, limit access to reporting features and monitor for suspicious log entries.

Recommended fix High confidence

FortiWeb 7.0.4 (for 7.0.x branch); FortiWeb 6.3.22 (for 6.3.x branch); or appropriate patched version for other branches

  1. Identify the currently installed FortiWeb version using the web UI or CLI command: 'get system status'
  2. Upgrade to the appropriate fixed version based on your current branch: For 7.0.x branch, upgrade to version 7.0.4 or later; For 6.3.x branch, upgrade to version 6.3.22 or later; For 6.4.x branch, upgrade to a version higher than 6.4.2; For 6.2.x branch, upgrade to a version higher than 6.2.7; For 6.0.x and 6.1.x branches, upgrade to a version that includes the fix
  3. Download the firmware from Fortinet's support portal: https://support.fortinet.com/
  4. Upload and install the new firmware via FortiWeb web interface (System > Maintenance > Firmware) or CLI
  5. After upgrade, verify the new version is installed: 'get system status'
  6. Review and clear any potentially malicious log entries that may have been injected before the fix
Caveat Point release upgrades typically do not have breaking changes; review Fortinet release notes for any known issues specific to your version

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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