FortiadcApplication · Fortinet
CVE-2025-54971
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 · uneditedAn exposure of sensitive information to an unauthorized actor vulnerability in Fortinet FortiADC 7.4.0, FortiADC 7.2 all versions, FortiADC 7.1 all versions, FortiADC 7.0 all versions, FortiADC 6.2 all versions may allow an admin with read-only permission to get the external resources password via the logs of the product
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 · moderate confidenceFortiADC logs expose external resource passwords to read-only admin users, allowing unauthorized access to sensitive credentials stored in system logs.
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
>= 6.2.0, < 7.4.3CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm FortiADC version is within affected rangeUse the CLI command 'get system status' or check the FortiADC GUI dashboard to identify the installed firmware versionAffected if Version is >= 6.2.0 and < 7.4.3
-
Verify presence of read-only admin accountsReview admin user configuration using 'get system admin' CLI command or check Users & Authentication > Admin Users in the GUIAffected if Any read-only admin accounts are configured in the system
-
Check log access permissionsReview log settings and access controls in the FortiADC GUI under Log & Report > Log Settings, or use 'get log' CLI commands to inspect who can access system logsAffected if Read-only admin users are permitted to view system logs
-
Inspect system logs for external resource passwordsAccess the system logs as a read-only admin would and search for patterns indicating stored credentials (passwords, keys, or secrets for external resources such as authentication servers, APIs, or backend systems)Affected if Logs contain plaintext or recoverable passwords for external resources
Your environment is affected if FortiADC runs a version between 6.2.0 and 7.4.3 and read-only admin users can access system logs containing external resource credentials
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.4.3
Restrict log access permissions and upgrade to a patched FortiADC version once available; audit all read-only admin accounts for unauthorized access.
FortiADC 7.4.3 or later
- Plan a maintenance window for the FortiADC upgrade
- Back up the current FortiADC configuration
- Upgrade FortiADC to version 7.4.3 or later
- After upgrade, verify the system is functioning correctly
- Confirm that read-only admin users can no longer view external resource passwords in logs
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortiadc
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54971 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-54971 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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