dbcve.org
FortiadcApplication · Fortinet

CVE-2022-38374

MEDIUM · 6.1 CVSS v3.1 Published 2022-11-02
Fix available
A fix is available. Upgrade to 6.2.4 / 7.0.3 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
A improper neutralization of input during web page generation ('cross-site scripting') in Fortinet FortiADC 7.0.0 - 7.0.2 and 6.2.0 - 6.2.4 allows an attacker to execute unauthorized code or commands via the URL and User fields observed in the traffic and event logviews.

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

This is a stored Cross-Site Scripting (XSS) vulnerability in Fortinet FortiADC web interface versions 7.0.0-7.0.2 and 6.2.0-6.2.4. The URL and User fields in traffic and event log views are not properly sanitized before rendering, allowing attackers to inject malicious JavaScript that executes in the context of other users' sessions when they view the logs.

MitigationUpgrade FortiADC to version 7.0.3 or later (for 7.x) or 6.2.5 or later (for 6.2.x). Alternatively, implement output encoding/HTML escaping on the log view rendering code for the URL and User fields to neutralize script execution.

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
FortiadcApplication
Affected:>= 6.2.0, < 6.2.4>= 7.0.0, < 7.0.3

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. Check FortiADC firmware version
    Execute 'get system status' via FortiADC CLI or check the Dashboard > Status page in the web UI to view the current firmware version.
    Affected if The installed version is 6.2.0 through 6.2.4, or 7.0.0 through 7.0.2.
  2. Verify web interface is enabled
    In the web UI, go to System > Settings > Administration Settings, or run 'show system interface' via CLI to confirm HTTP/HTTPS management access is enabled.
    Affected if HTTP or HTTPS management access is enabled, making the web interface reachable.
  3. Confirm log viewing access is configured
    Navigate to Log & Report > Traffic Log or Event Log in the web UI, or use 'execute log filter' CLI commands to verify logging and log viewing capabilities are active.
    Affected if Traffic logging or event logging is enabled and users have permission to view logs through the web interface.

You are affected if your FortiADC runs version 6.2.0-6.2.4 or 7.0.0-7.0.2, the web interface is accessible, and users can view traffic or event logs where the URL and User fields are rendered unsanitized.

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 / 7.0.3 or later
Fixed in 6.2.47.0.3
Interim mitigation

Upgrade FortiADC to version 7.0.3 or later (for 7.x) or 6.2.5 or later (for 6.2.x). Alternatively, implement output encoding/HTML escaping on the log view rendering code for the URL and User fields to neutralize script execution.

Recommended fix High confidence

FortiADC 6.2.4+ or 7.0.3+ (depending on current branch)

  1. 1. Identify the current FortiADC version by navigating to Dashboard > System Information in the web UI or running 'get system status' in the CLI
  2. 2. If running FortiADC 6.2.x (versions 6.2.0 through 6.2.3), plan to upgrade to version 6.2.4 or later
  3. 3. If running FortiADC 7.0.x (versions 7.0.0 through 7.0.2), plan to upgrade to version 7.0.3 or later
  4. 4. Back up the current FortiADC configuration using System > Maintenance > Backup & Restore in the web UI or 'execute backup full-config' in the CLI
  5. 5. Download the appropriate firmware upgrade from Fortinet customer support portal or FortiGuard
  6. 6. Apply the firmware upgrade via System > Firmware in the web UI or 'execute system firmware-upgrade' in the CLI
  7. 7. After upgrade, verify the new version is installed and confirm the web UI is accessible
  8. 8. Validate that the configuration was preserved and test critical functionality
Caveat Major version upgrades (e.g., 6.x to 7.x) may introduce breaking changes; review Fortinet release notes and test in non-production environment before deploying

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

Fix this in Fortiadc 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-38374 — 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-38374 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