dbcve.org
FortiadcApplication · Fortinet

CVE-2022-43952

MEDIUM · 5.4 CVSS v3.1 Published 2023-04-11
Fix available
A fix is available. Upgrade to 6.2.6 / 7.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 ('Cross-site Scripting') vulnerability [CWE-79] in FortiADC version 7.1.1 and below, version 7.0.3 and below, version 6.2.5 and below may allow an authenticated attacker to perform a cross-site scripting attack via 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 confidence

A stored Cross-Site Scripting (XSS) vulnerability in FortiADC web interface allows authenticated attackers to inject malicious JavaScript via crafted HTTP requests. The payload persists and executes when other authenticated users view the affected page.

MitigationApply vendor patches: upgrade to FortiADC 7.1.2, 7.0.4, 6.2.6 or later to remediate the XSS vulnerability.

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.6>= 7.0.0, < 7.0.4>= 7.1.0, < 7.1.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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm FortiADC deployment
    Identify if FortiADC is deployed in your environment. This is a Fortinet application layer load balancer. Check network inventory or look for fortiadc processes/services.
    Affected if FortiADC is in use and the web interface is accessible
  2. Check FortiADC version via CLI
    Log into the FortiADC CLI and run: get system status. This displays the firmware version.
    Affected if The displayed version falls within 6.2.0 to 6.2.5, 7.0.0 to 7.0.3, or 7.1.0 to 7.1.1
  3. Check FortiADC version via web UI
    Log into the FortiADC web UI. The version is displayed on the login page or in the Dashboard > System Information widget.
    Affected if The displayed version falls within 6.2.0 to 6.2.5, 7.0.0 to 7.0.3, or 7.1.0 to 7.1.1
  4. Verify web interface is enabled
    In the web UI, go to System > Settings > Admin Settings. Confirm the HTTPS administrative interface is enabled.
    Affected if Web interface is enabled and the version is in the affected ranges listed above

You are affected if your FortiADC version is 6.2.0-6.2.5, 7.0.0-7.0.3, or 7.1.0-7.1.1 and the web interface is enabled.

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.6 / 7.0.4 / 7.1.2 or later
Fixed in 6.2.67.0.47.1.2
Interim mitigation

Apply vendor patches: upgrade to FortiADC 7.1.2, 7.0.4, 6.2.6 or later to remediate the XSS vulnerability.

Recommended fix High confidence

FortiADC 6.2.6, 7.0.4, or 7.1.2 (depending on your current version branch)

  1. Identify the current FortiADC version via the web UI (Dashboard > Status) or CLI: get system status
  2. Determine which version branch you are currently running (6.2.x, 7.0.x, or 7.1.x)
  3. Backup the current FortiADC configuration via Web UI (System > Config > Backup) or CLI: execute backup config tftp <filename]
  4. Schedule a maintenance window for the upgrade
  5. For FortiADC 6.2.x: Upgrade to version 6.2.6 or later
  6. For FortiADC 7.0.x: Upgrade to version 7.0.4 or later
  7. For FortiADC 7.1.x: Upgrade to version 7.1.2 or later
  8. Upload the firmware via Web UI (System > Firmware > Upgrade) or via CLI: execute firmware upgrade <image>
Caveat Standard Fortinet firmware upgrade - review release notes for any configuration changes or behavior differences between versions; ensure compatibility with connected Fortinet devices

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

Fix this in Fortiadc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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 locally
dbcve dependency scanner

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