Secure Firewall Management CenterApplication · Cisco

CVE-2023-20206

MEDIUM · 6.1 CVSS v3.1 Published 2023-11-01
Fix available
A fix is available. Upgrade to after 7.3.1.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Multiple vulnerabilities in the web-based management interface of Cisco Firepower Management Center (FMC) Software could allow an unauthenticated, remote attacker to conduct a stored cross-site scripting (XSS) attack against a user of the interface of an affected device. These vulnerabilities are due to insufficient validation of user-supplied input by the web-based management interface. An attacker could exploit these vulnerabilities by inserting crafted input into various data fields in an affected interface. A successful exploit could allow the attacker to execute arbitrary script code in the context of the interface, or access sensitive, browser-based information. In some cases, it is also possible to cause a temporary availability impact to portions of the FMC Dashboard.

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 confidence

Multiple stored XSS vulnerabilities exist in Cisco Firepower Management Center's web-based management interface due to insufficient validation of user-supplied input. An unauthenticated remote attacker can inject malicious scripts into data fields, which are then stored and executed in the context of other users' browsers when they access the affected interface, potentially allowing access to sensitive browser-based information or causing temporary dashboard availability impacts.

MitigationApply the appropriate Cisco software update for FMC when available; in the interim, restrict network access to the management interface to trusted users only and monitor for suspicious input patterns in data fields.

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
Secure Firewall Management CenterApplication
Affected:>= 6.6.0, <= 6.6.7.1>= 6.7.0, <= 6.7.0.3>= 7.0.0, <= 7.0.5>= 7.1.0, <= 7.1.0.3>= 7.2.0, <= 7.2.4>= 7.3.0, <= 7.3.1.1

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 Cisco FMC product and version
    Access the Firepower Management Center web interface and navigate to Help > About, or log into the device CLI and run 'show version' to determine the exact software version
    Affected if The installed version falls within these ranges: 6.6.0 to 6.6.7.1, 6.7.0 to 6.7.0.3, 7.0.0 to 7.0.5, 7.1.0 to 7.1.0.3, 7.2.0 to 7.2.4, or 7.3.0 to 7.3.1.1
  2. Verify web management interface exposure
    Confirm whether the FMC web-based management interface is accessible from network segments that include untrusted or external users
    Affected if The management interface is reachable by unauthenticated or untrusted users on the network
  3. Inspect stored data fields for injected scripts
    Review dashboard widgets, saved policies, object definitions, and configuration fields within the FMC web interface for unexpected script tags, encoded characters, or suspicious content that does not belong to your legitimate configuration
    Affected if Any stored data fields contain malicious script payloads that could be executed in other users' browser sessions

Your environment is affected if the FMC version is within the listed ranges AND the web management interface is accessible to untrusted users, allowing potential injection of malicious scripts into stored data fields.

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.3.1.1
Interim mitigation

Apply the appropriate Cisco software update for FMC when available; in the interim, restrict network access to the management interface to trusted users only and monitor for suspicious input patterns in data fields.

Recommended fix Moderate confidence

Upgrade to FMC version 7.1.0.4 or later, or 7.2.x/7.3.x (latest stable release) - Cisco has released fixed versions beyond the affected branches (7.1.0.3 and earlier)

  1. 1. Identify the current version of Secure Firewall Management Center by navigating to the FMC web interface and checking the System > Updates page or the dashboard for version information.
  2. 2. Determine which version branch (6.6.x, 6.7.x, 7.0.x, or 7.1.x) your current installation is running on.
  3. 3. Download the appropriate fixed FMC software version from the Cisco Software Download center (software.cisco.com) or your Cisco smart account.
  4. 4. Plan for a maintenance window as the upgrade will require downtime; schedule accordingly.
  5. 5. Back up the FMC configuration before proceeding with the upgrade.
  6. 6. Install the upgraded FMC software version using the web-based management interface or CLI, following Cisco's upgrade procedure documentation.
  7. 7. After upgrade, verify the new version is installed and confirm the CVE-2023-20206 vulnerability is resolved by checking the Cisco Security Advisory.
Caveat Review Cisco FMC upgrade guide for compatibility requirements; some upgrades may require intermediate steps if jumping multiple major versions; ensure dependent devices (Firepower sensors) are compatible with the target FMC version

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

Fix this in Secure Firewall Management Center Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20206 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