CVE-2025-47855
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 [CWE-200] vulnerability in Fortinet FortiFone 7.0.0 through 7.0.1, FortiFone 3.0.13 through 3.0.23 allows an unauthenticated attacker to obtain the device configuration via crafted HTTP or HTTPS 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 · moderate confidenceAn unauthenticated attacker can obtain the full device configuration of FortiFone 7.0.0-7.0.1 and 3.0.13-3.0.23 devices by sending crafted HTTP/HTTPS requests. The configuration likely contains sensitive information including credentials, network settings, and system parameters, exposing the device to further compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify FortiFone devices on the networkScan the network for devices responding on HTTP (port 80) and HTTPS (port 443) that present FortiFone web management interfaces. Note the IP addresses of discovered FortiFone units.Affected if Any FortiFone device matching versions 7.0.0-7.0.1 or 3.0.13-3.0.23 is present on the network
-
Determine the installed FortiFone firmware versionAccess the FortiFone admin interface via HTTPS and navigate to System > Firmware or About section to view the running firmware version. Alternatively, check the device directly or review asset inventory records.Affected if The firmware version is 7.0.0 through 7.0.1 or 3.0.13 through 3.0.23 (inclusive)
-
Verify management interface network exposureDetermine whether the FortiFone HTTP/HTTPS management ports are accessible from network segments that contain untrusted or external users (e.g., the internet, guest networks). Use port scanning from an external perspective or review firewall rules governing access to the device.Affected if The management interface is reachable from untrusted networks without authentication barriers
-
Review access logs for unauthenticated configuration requestsExamine FortiFone access logs, web server logs, or upstream firewall logs for HTTP/HTTPS requests to configuration endpoints that occurred without prior authentication. Look for requests to paths that return device configuration data.Affected if Logs show configuration retrieval requests from unauthenticated or unexpected IP addresses
A user is affected if they have any FortiFone device running firmware version 7.0.0-7.0.1 or 3.0.13-3.0.23 with its management interface exposed to the network, as the vulnerability allows unauthenticated configuration disclosure.
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.
From vendor dataApply vendor-supplied firmware patches to upgrade vulnerable FortiFone devices to fixed versions. Until patched, restrict external access to HTTP/HTTPS management interfaces using firewall rules or VPNs.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47855 — 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-47855 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