dbcve.org
FortiproxyApplication · Fortinet

CVE-2023-26207

MEDIUM · 6.5 CVSS v3.1 Published 2023-06-13
Fix available
A fix is available. Upgrade to after 7.2.4 or later.
See remediation →
71/100
Remediation priority · Elevated
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
An insertion of sensitive information into log file vulnerability in Fortinet FortiOS 7.2.0 through 7.2.4 and FortiProxy 7.0.0 through 7.0.10. 7.2.0 through 7.2.1 allows an attacker to read certain passwords in plain text.

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 7.2.0-7.2.4 and FortiProxy 7.0.0-7.0.10 contain a vulnerability where certain passwords are written in plain text to log files, allowing unauthorized users with log access to read sensitive credentials in plaintext.

MitigationUpgrade to FortiOS 7.2.5 or later and FortiProxy 7.0.11 or later. Review existing log files for exposed credentials and restrict access to log storage.

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.0.0, <= 7.0.10= 7.2.0= 7.2.1
FortiosOperating system
Affected:>= 7.2.0, <= 7.2.4

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed FortiOS version
    Run 'get system status' or 'fw -version' via CLI to retrieve the FortiOS firmware version
    Affected if The version falls within 7.2.0 through 7.2.4
  2. Identify the installed FortiProxy version
    Run 'get system status' or check the FortiProxy GUI dashboard for the firmware version
    Affected if The version falls within 7.0.0 through 7.0.10, or equals 7.2.0 or 7.2.1
  3. Verify logging is enabled
    Check the logging configuration via 'get log syslogd setting' or 'get log syslogd2 setting' in the FortiOS/FortiProxy CLI
    Affected if Remote syslog or local logging is configured and active
  4. Inspect log files for plaintext credentials
    Review log files in /var/log/ or the configured log storage location for password strings in plain text
    Affected if Log files contain visible plaintext passwords in configuration or authentication events
  5. Assess log file access controls
    Verify file permissions on the log directory and review which users or groups have read access to logs
    Affected if Unprivileged or unauthorized users have read access to system logs

You are affected if your FortiOS version is 7.2.0-7.2.4 or FortiProxy version is 7.0.0-7.0.10/7.2.0-7.2.1, and your logs contain plaintext passwords accessible to unauthorized 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 a release after 7.2.4
Interim mitigation

Upgrade to FortiOS 7.2.5 or later and FortiProxy 7.0.11 or later. Review existing log files for exposed credentials and restrict access to log storage.

Recommended fix Moderate confidence

FortiOS: 7.2.5 or later (recommended latest stable 7.4.x); FortiProxy 7.0.11+ or 7.2.2+

  1. 1. Identify the Fortinet device model and current firmware version using the GUI or CLI (get system status)
  2. 2. For FortiOS devices: Upgrade to FortiOS 7.2.5 or later, or the latest stable 7.4.x release
  3. 3. For FortiProxy devices: If on 7.0.x, upgrade to FortiProxy 7.0.11 or later. If on 7.2.x, upgrade to FortiProxy 7.2.2 or later
  4. 4. After upgrade, verify the fix by checking system logs to confirm sensitive data (passwords) are no longer logged in plain text
  5. 5. Review all log configurations and ensure compliance with log sanitization settings
Caveat Review release notes for your specific model before upgrading; some hardware may have older firmware ceiling restrictions

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

Fix this in Fortiproxy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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