mediumCVE-2026-23573

CVE-2026-23573 in FortiProxy and FortiOS

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.

ProductFortiProxy and FortiOS
CVSS6.1
EPSSNot scored yet
UpdatedJuly 15, 2026

Quick answer

Fortinet FortiProxy and FortiOS should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • FortiProxy and FortiOS versions listed in Fortinet advisory FG-IR-26-150
  • FortiProxy 7.6.0 through 7.6.6, 7.4 all versions, and 7.2 all versions

Fixed versions

  • Latest vendor-supported fixed release listed in Fortinet advisory FG-IR-26-150

How to fix it

CVE-2026-23573 affects FortiProxy and FortiOS. In simple terms, a user may open a page that runs unsafe script. Fix it by updating to Latest vendor-supported fixed release listed in Fortinet advisory FG-IR-26-150. If this system is online or used by admins, treat the fix as urgent.

  1. Find every place where FortiProxy and FortiOS is installed or used.
  2. Check if the version matches: FortiProxy and FortiOS versions listed in Fortinet advisory FG-IR-26-150; FortiProxy 7.6.0 through 7.6.6, 7.4 all versions, and 7.2 all versions.
  3. Update or apply the vendor fix: Latest vendor-supported fixed release listed in Fortinet advisory FG-IR-26-150.
  4. If you cannot update today, allow only trusted users and trusted networks.
  5. Turn off the affected feature or plugin if the vendor says that is safe to do.
  6. Check logs for crashes, strange requests, new admin actions, or unexpected access.
  7. Change secrets or passwords if you think data or admin access may have been exposed.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version or mitigation matches: Latest vendor-supported fixed release listed in Fortinet advisory FG-IR-26-150.
  • Confirm the affected feature is no longer exposed to untrusted users.
  • Run the affected workflow again and make sure it still works.
  • Review logs again after the fix for repeated suspicious activity.
  • Run a new Fixnx scan if this software is part of a public website.
  • Save the advisory link and proof of the fix in your change record.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-23573?

Fortinet FortiProxy and FortiOS versions listed as affected should be reviewed: FortiProxy and FortiOS versions listed in Fortinet advisory FG-IR-26-150, FortiProxy 7.6.0 through 7.6.6, 7.4 all versions, and 7.2 all versions.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.