dbcve.org
FortiadcApplication · Fortinet

CVE-2023-25603

CRITICAL · 9.1 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to after 6.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 permissive cross-domain policy with untrusted domains vulnerability in Fortinet FortiADC 7.1.0 - 7.1.1, FortiDDoS-F 6.3.0 - 6.3.4 and 6.4.0 - 6.4.1 allow an unauthorized attacker to carry out privileged actions and retrieve sensitive information via crafted web 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 permissive cross-domain policy in FortiADC 7.1.0-7.1.1 and FortiDDoS-F 6.3.0-6.3.4/6.4.0-6.4.1 allows untrusted external domains to make privileged web requests, enabling unauthorized actions and sensitive data exfiltration.

MitigationRestrict cross-domain policies to explicitly trusted domains only, or disable cross-domain access if not required, and validate all cross-origin requests server-side.

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:= 7.1.0= 7.1.1
Fortiddos FApplication
Affected:>= 6.3.0, <= 6.3.4= 6.4.0= 6.4.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 product and version
    Access the FortiADC or FortiDDoS-F CLI or web interface and run the command to display the system version, typically 'get system status' or 'version' in CLI, or check About/Status page in web UI
    Affected if The displayed version matches FortiADC 7.1.0 or 7.1.1, or FortiDDoS-F version 6.3.0 through 6.3.4, 6.4.0, or 6.4.1
  2. Locate cross-domain policy settings
    In the web UI, navigate to System > Settings or Web Application Firewall > Cross-Domain Policy. In CLI, look for 'cross-domain' or 'cors' related configuration under the appropriate config tree
    Affected if Cross-domain policy configuration section exists and is accessible
  3. Inspect allowed origins configuration
    Review the cross-domain policy configuration for 'allowed-origin', 'allow-origin', or 'trusted-domains' settings. List all domains or origins configured as allowed
    Affected if The policy contains wildcard '*' or includes untrusted/external domains not explicitly verified by your organization
  4. Verify credential transmission setting
    Check if 'allow-credentials' or similar setting is enabled in the cross-domain policy, which permits cookies or authorization headers to be sent with cross-origin requests
    Affected if Credential transmission is enabled alongside a permissive origin list containing untrusted domains
  5. Confirm web UI/API exposure
    Verify that the management web interface or REST API is exposed to untrusted networks, as the flaw requires the web service to be accessible
    Affected if The web interface is reachable from networks outside your trusted zone and the cross-domain policy is permissive

Your environment is affected if you run FortiADC 7.1.0-7.1.1 or FortiDDoS-F 6.3.0-6.3.4/6.4.0-6.4.1 and the cross-domain policy allows untrusted or wildcard origins to make requests with credentials.

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.

From vendor data
Upgrade available Upgrade to a release after 6.3.4
Interim mitigation

Restrict cross-domain policies to explicitly trusted domains only, or disable cross-domain access if not required, and validate all cross-origin requests server-side.

Fix this in Fortiadc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
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,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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