dbcve.org
FortiproxyApplication · Fortinet

CVE-2025-22252

HIGH · 7.2 CVSS v3.1 Published 2025-05-28
Fix available
A fix is available. Upgrade to 7.4.7 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

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 missing authentication for critical function in Fortinet FortiProxy versions 7.6.0 through 7.6.1, FortiSwitchManager version 7.2.5, and FortiOS versions 7.4.4 through 7.4.6 and version 7.6.0 may allow an attacker with knowledge of an existing admin account to access the device as a valid admin via an authentication bypass.

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

FortiOS, FortiProxy, and FortiSwitchManager contain a missing authentication for critical function that allows an attacker with knowledge of an existing admin account to bypass authentication and gain full admin access to the device. This is a high-severity authentication bypass where the attacker already knows the admin username but can circumvent password verification.

MitigationApply vendor-released patches/upgrades to the affected versions. Additionally, restrict admin account access to trusted IP addresses via FortiOS administrative access policies and minimize exposure of admin account credentials.

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.6.0
FortiswitchmanagerApplication
Affected:= 7.2.5
FortiosOperating system
Affected:>= 7.4.4, < 7.4.7= 7.6.0

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

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 FortiOS version
    Run CLI command: get system status - look for Version line
    Affected if Version is 7.4.4 through 7.4.6, or version is 7.6.0
  2. Check FortiProxy version
    Run CLI command: get system status - look for Version line
    Affected if Version is 7.6.0
  3. Check FortiSwitchManager version
    Run CLI command: get system status - look for Version line
    Affected if Version is 7.2.5
  4. Verify admin accounts exist
    Run CLI command: get admin user - confirms at least one admin account is configured
    Affected if One or more admin accounts are configured and version is in affected range

Your environment is affected if the installed FortiOS, FortiProxy, or FortiSwitchManager version matches one of the affected versions listed and at least one admin account is configured.

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 7.4.7 or later
Fixed in 7.4.7
Interim mitigation

Apply vendor-released patches/upgrades to the affected versions. Additionally, restrict admin account access to trusted IP addresses via FortiOS administrative access policies and minimize exposure of admin account credentials.

Recommended fix High confidence

FortiOS 7.4.7+ or 7.6.1+; FortiProxy 7.6.1+; FortiSwitchManager 7.2.6+

  1. 1. Identify the currently installed Fortinet product and version (FortiOS, FortiProxy, or FortiSwitchManager)
  2. 2. For FortiOS 7.4.x versions (7.4.4 through 7.4.6), upgrade to FortiOS 7.4.7 or later
  3. 3. For FortiOS 7.6.0, upgrade to FortiOS 7.6.1 or later
  4. 4. For FortiProxy 7.6.0, upgrade to FortiProxy 7.6.1 or later
  5. 5. For FortiSwitchManager 7.2.5, upgrade to FortiSwitchManager 7.2.6 or later
  6. 6. After upgrade, verify the authentication mechanism functions correctly and restrict admin account access to trusted users only
  7. 7. Review admin account logs for any suspicious activity that may indicate exploitation attempts
Caveat Review release notes for your specific version upgrade path for any configuration or feature changes

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
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,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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