dbcve.org
FortiosOperating system · Fortinet

CVE-2025-22862

MEDIUM · 6.7 CVSS v3.1 Published 2025-10-02
Fix available
A fix is available. Upgrade to 7.2.12 / 7.4.8 or later.
See remediation →
69/100
Remediation priority · Elevated
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
An Authentication Bypass Using an Alternate Path or Channel vulnerability [CWE-288] in FortiOS 7.4.0 through 7.4.7, 7.2.0 through 7.2.11, 7.0.6 and above; and FortiProxy 7.6.0 through 7.6.2, 7.4.0 through 7.4.8, 7.2 all versions, 7.0.5 and above may allow an authenticated attacker to elevate their privileges via triggering a malicious Webhook action in the Automation Stitch component.

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

An authenticated attacker with access to FortiOS or FortiProxy can exploit the Automation Stitch webhook functionality to elevate privileges by triggering malicious webhook actions. This is an authenticated privilege escalation (CWE-288) affecting the Automation Stitch component.

MitigationUpgrade to FortiOS 7.4.8+, 7.2.12+, 7.0.7+ and FortiProxy 7.4.9+, 7.6.3+, 7.0.6+ per vendor advisories. Limit administrative access to Automation Stitch configurations and restrict webhook endpoint access.

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
FortiosOperating system
Affected:>= 7.0.6, < 7.2.12>= 7.4.0, < 7.4.8
FortiproxyApplication
Affected:>= 7.0.5, < 7.4.9>= 7.6.0, < 7.6.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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Identify FortiOS or FortiProxy version
    Run 'get system status' via CLI or check the web UI dashboard to retrieve the firmware version.
    Affected if The version falls within any of these ranges: FortiOS 7.0.6 to <7.0.7, 7.0.7 to <7.2.12, 7.4.0 to <7.4.8; FortiProxy 7.0.5 to <7.0.6, 7.0.6 to <7.4.9, 7.6.0 to <7.6.3.
  2. Confirm Automation Stitch is configured
    Run 'diagnose system automation list' via CLI or review System > FortiView > Automation in the web UI to list active automation stitches.
    Affected if Any Automation Stitch is enabled or configured on the device.
  3. Check for webhook action in automation stitches
    Run 'show system automation-action' via CLI to review all automation actions. Look for action-type 'webhook' or 'Webhook' in the configuration.
    Affected if Any automation action is configured with webhook type pointing to external endpoints.
  4. Review administrative users with automation access
    Run 'show system admin' via CLI and check the 'trusthost' or 'accprofile' settings. Verify which admin profiles have access to 'system' > 'automation' resources.
    Affected if Multiple administrative accounts exist, or admin profiles with automation configuration rights are granted to non-root/admin users.
  5. Audit recent automation stitch modifications
    Run 'diagnose system automation history' via CLI to view recent automation stitch executions and changes.
    Affected if Unexpected or unauthorized automation stitches were recently created, modified, or executed.

A user is affected if their FortiOS or FortiProxy version is within the affected ranges AND the Automation Stitch feature with webhook actions is configured or accessible to non-privileged 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 7.2.12 / 7.4.8 / 7.4.9 or later
Fixed in 7.2.127.4.87.4.9
Interim mitigation

Upgrade to FortiOS 7.4.8+, 7.2.12+, 7.0.7+ and FortiProxy 7.4.9+, 7.6.3+, 7.0.6+ per vendor advisories. Limit administrative access to Automation Stitch configurations and restrict webhook endpoint access.

Recommended fix High confidence

FortiOS: 7.2.12+ or 7.4.8+ | FortiProxy: 7.4.9+ or 7.6.3+

  1. 1. Identify the current FortiOS or FortiProxy version running on the device using the CLI command: get system status
  2. 2. For FortiOS: If running 7.0.x (>=7.0.6), upgrade to FortiOS 7.2.12 or later, or upgrade to FortiOS 7.4.8 or later
  3. 3. For FortiOS: If running 7.2.x (>=7.2.0, <7.2.12), upgrade to FortiOS 7.2.12 or later
  4. 4. For FortiOS: If running 7.4.x (>=7.4.0, <7.4.8), upgrade to FortiOS 7.4.8 or later
  5. 5. For FortiProxy: If running 7.0.x (>=7.0.5), upgrade to FortiProxy 7.4.9 or later, or upgrade to 7.6.3 or later
  6. 6. For FortiProxy: If running 7.2.x (all versions), upgrade to FortiProxy 7.4.9 or later, or upgrade to 7.6.3 or later
  7. 7. For FortiProxy: If running 7.4.x (>=7.4.0, <7.4.9), upgrade to FortiProxy 7.4.9 or later
  8. 8. For FortiProxy: If running 7.6.x (>=7.6.0, <7.6.3), upgrade to FortiProxy 7.6.3 or later
Caveat Review release notes for upgrade considerations; ensure compatibility with other Fortinet components in your environment

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

Fix this in Fortios Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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