dbcve.org
FortiwebApplication · Fortinet

CVE-2024-23107

MEDIUM · 5.5 CVSS v3.1 Published 2024-06-03
Fix available
A fix is available. Upgrade to 7.0.9 / 7.2.5 or later.
See remediation →
57/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 exposure of sensitive information to an unauthorized actor vulnerability [CWE-200] in FortiWeb version 7.4.0, version 7.2.4 and below, version 7.0.8 and below, 6.3 all versions may allow an authenticated attacker to read password hashes of other administrators via CLI commands.

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

FortiWeb versions 7.4.0, 7.2.4 and below, 7.0.8 and below, and 6.3 all versions contain a CWE-200 vulnerability where an authenticated attacker with administrative access can read password hashes of other administrators through specific CLI commands. This allows privilege escalation by obtaining hashed credentials of other admin accounts.

MitigationApply the appropriate FortiWeb firmware update from Fortinet's security advisory. If immediate patching is not possible, restrict CLI access to trusted administrators and monitor for unauthorized access to admin accounts.

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
FortiwebApplication
Affected:>= 6.3.0, <= 6.3.23>= 7.0.0, < 7.0.9>= 7.2.0, < 7.2.5= 7.4.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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/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 installed FortiWeb version
    Run the command 'get system status' or 'FWB # get system status' in the FortiWeb CLI to retrieve the firmware version
    Affected if The displayed version falls within these ranges: 6.3.0 to 6.3.23, 7.0.0 to 7.0.8, 7.2.0 to 7.2.4, or exactly 7.4.0
  2. Verify presence of multiple admin accounts
    Run 'get system admin' in FortiWeb CLI to list all configured administrator accounts
    Affected if Multiple admin accounts exist and the device is running an affected version, making additional accounts vulnerable to hash extraction
  3. Review CLI audit logs for sensitive command access
    Run 'execute log filter category event' and then 'execute log display' to review CLI command history, looking for commands that access admin password data
    Affected if Logs show execution of commands that retrieve admin password hashes or configuration data from other admin accounts
  4. Check for unauthorized admin sessions or privilege escalation
    Run 'get system admin session' in CLI to view active and recent admin login sessions
    Affected if Sessions show admin accounts logging in from unexpected sources or times, indicating potential exploitation of harvested credentials

You are affected if your FortiWeb version is 6.3.0 through 6.3.23, 7.0.0 through 7.0.8, 7.2.0 through 7.2.4, or exactly 7.4.0 and multiple admin accounts exist in the system.

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.0.9 / 7.2.5 or later
Fixed in 7.0.97.2.5
Interim mitigation

Apply the appropriate FortiWeb firmware update from Fortinet's security advisory. If immediate patching is not possible, restrict CLI access to trusted administrators and monitor for unauthorized access to admin accounts.

Recommended fix High confidence

FortiWeb 7.0.9+ (for 7.0.x), 7.2.5+ (for 7.2.x), 7.4.1+ (for 7.4.x), or migrate from 6.3.x to 7.0.9+/7.2.5+

  1. 1. Identify the currently installed FortiWeb version using the CLI command: get system status
  2. 2. For FortiWeb 6.3.x deployments: Upgrade to FortiWeb 7.0.9 or later (6.3.x has no fix; migration to 7.0.x or 7.2.x is required)
  3. 3. For FortiWeb 7.0.x deployments: Upgrade to version 7.0.9 or later
  4. 4. For FortiWeb 7.2.x deployments: Upgrade to version 7.2.5 or later
  5. 5. For FortiWeb 7.4.0 deployments: Upgrade to version 7.4.1 or later
  6. 6. After upgrade, verify the fix by confirming the system version and reviewing release notes for the security fix
  7. 7. Review administrator account permissions and audit logs to ensure no unauthorized access occurred
Caveat Major version upgrades (6.3 to 7.x) may introduce configuration or behavioral changes; review Fortinet migration guides before upgrading

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

Fix this in Fortiweb Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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