Iot Field Network DirectorApplication · Cisco
CVE-2020-26072
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 · uneditedA vulnerability in the SOAP API of Cisco IoT Field Network Director (FND) could allow an authenticated, remote attacker to access and modify information on devices that belong to a different domain. The vulnerability is due to insufficient authorization in the SOAP API. An attacker could exploit this vulnerability by sending SOAP API requests to affected devices for devices that are outside their authorized domain. A successful exploit could allow the attacker to access and modify information on devices that belong to a different domain.
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 confidenceA vulnerability in the SOAP API of Cisco IoT Field Network Director (FND) allows authenticated remote attackers to access and modify information on devices outside their authorized domain due to insufficient authorization checks in the SOAP API endpoint.
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
Iot Field Network DirectorApplication
< 4.6.1CVSS 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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cisco IoT Field Network Director is installedInventory your systems for the presence of Cisco IoT Field Network Director software; check running services or installed applications for 'IoT Field Network Director' or 'FND'Affected if The software is present in the environment
-
Check installed version numberLocate the FND version information through the web UI (typically in Help > About or System > Management), CLI show command, or installation directory; compare against 4.6.1Affected if Installed version is lower than 4.6.1
-
Verify SOAP API is enabledAccess the FND administration interface and check SOAP API service settings or review the FND configuration for SOAP API endpoint availability; look for 'SOAP' or 'API' service status in system servicesAffected if SOAP API is enabled and accessible
-
Inspect SOAP API authorization domain configurationIn the FND web UI, navigate to the SOAP API settings or user/device domain assignments; verify whether domain-based access controls restrict SOAP API users to specific device domainsAffected if SOAP API lacks proper domain-based authorization controls or allows cross-domain access
-
Review SOAP API access logs for cross-domain activityExamine FND audit or access logs for SOAP API calls where users accessed or modified devices outside their assigned domain; look for anomalous device domain interactionsAffected if Evidence exists of cross-domain SOAP API access by users outside their authorized domain
You are affected if Cisco IoT FND is installed with version lower than 4.6.1 and the SOAP API is enabled with insufficient domain-based authorization controls.
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 data4.6.1
Apply the vendor patch from Cisco for CVE-2020-26072; until then, enforce strict network segmentation and domain-based access controls to limit cross-domain SOAP API access.
Fix this in Iot Field Network Director
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26072 — 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-2020-26072 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