dbcve.org
FortiproxyApplication · Fortinet

CVE-2026-23573

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 1.8.1 / 7.2.10 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 5 weeks old

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] vulnerability in Fortinet FortiOS 7.6.0 through 7.6.6, FortiOS 7.4 all versions, FortiOS 7.2 all versions, FortiPAM 1.8.0, FortiPAM 1.7 all versions, FortiPAM 1.6 all versions, FortiPAM 1.5 all versions, FortiPAM 1.4 all versions, FortiPAM 1.3 all versions, FortiPAM 1.2 all versions, FortiPAM 1.1 all versions, FortiPAM 1.0 all versions, FortiProxy 7.4.0 through 7.4.3, FortiProxy 7.2.0 through 7.2.9 may allow an authenticated remote user to execute code or commands via crafted 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 (CWE-79) in Fortinet FortiOS, FortiPAM, and FortiProxy allows authenticated remote users to execute arbitrary JavaScript or commands via crafted requests. The vulnerability exists in web page generation routines where user-supplied input is improperly sanitized before being rendered.

MitigationUpgrade FortiOS, FortiPAM, or FortiProxy to the vendor-provided patched version. If immediate patching is not feasible, restrict administrative access to trusted IP addresses and implement Web Application Firewall (WAF) rules to filter malicious XSS payloads.

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
FortiproxyApplication
Affected:>= 7.2.0, < 7.2.10>= 7.4.0, < 7.4.4
FortiosOperating system
Affected:>= 7.2.0, < 7.6.7
FortipamOperating system
Affected:>= 1.0.0, < 1.8.1

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 the Fortinet product
    Access the CLI and run 'get system status' or check the web UI dashboard to confirm whether the device is running FortiOS, FortiPAM, or FortiProxy
    Affected if The product is FortiOS, FortiPAM, or FortiProxy and the version falls within the affected ranges
  2. Determine the installed firmware version
    Run 'get system status' in the FortiOS/FortiProxy CLI, or for FortiPAM access the web UI under System > Firmware to view the running version
    Affected if The version is FortiOS >= 7.2.0 and < 7.6.7, FortiPAM >= 1.0.0 and < 1.8.1, or FortiProxy >= 7.2.0 to < 7.2.10 or >= 7.4.0 to < 7.4.4
  3. Verify web management interface is enabled
    In the CLI run 'get system interface' or check in web UI under Network > Interfaces to confirm the administrative web interface (HTTP/HTTPS) is enabled on any interface
    Affected if The web UI is accessible and accepts authenticated sessions - this is required for the XSS to be exploitable
  4. Confirm remote administrative access is permitted
    Run 'show system admin' and check for admin users with remote-accessible profiles, or check Network > Interface settings for 'HTTPS' or 'HTTP' access enabled on external-facing interfaces
    Affected if Authenticated remote users can access the web interface - this is required for the stored XSS to be triggered

You are affected if you are running FortiOS 7.2.0 through 7.6.6, FortiPAM 1.0.0 through 1.8.0, or FortiProxy 7.2.0 through 7.2.9 or 7.4.0 through 7.4.3, and the web administrative interface is accessible to authenticated users.

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 1.8.1 / 7.2.10 / 7.4.4 or later
Fixed in 1.8.17.2.107.4.4
Interim mitigation

Upgrade FortiOS, FortiPAM, or FortiProxy to the vendor-provided patched version. If immediate patching is not feasible, restrict administrative access to trusted IP addresses and implement Web Application Firewall (WAF) rules to filter malicious XSS payloads.

Recommended fix High confidence

FortiOS: 7.6.7+ / 7.4.4+ / 7.2.10+ | FortiProxy: 7.4.4+ / 7.2.10+ | FortiPAM: 1.8.1+

  1. Identify the affected Fortinet product (FortiOS, FortiProxy, or FortiPAM) in your environment
  2. Check the current installed version using the FortiOS CLI command 'get system status' or equivalent for your product
  3. For FortiOS: Upgrade to version 7.6.7 or later, or 7.4.4 or later, or 7.2.10 or later depending on your support lifecycle
  4. For FortiProxy: Upgrade to version 7.2.10 or later, or 7.4.4 or later depending on your current branch
  5. For FortiPAM: Upgrade to version 1.8.1 or later
  6. Schedule a maintenance window and backup current configuration before upgrading
  7. After upgrade, verify the version change and test functionality
Caveat Major version upgrades may introduce configuration changes; review Fortinet release notes before upgrading

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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