dbcve.org
Sd Wan VmanageApplication · Cisco

CVE-2021-1225

CRITICAL · 9.1 CVSS v3.1 Published 2021-01-20
Fix available
A fix is available. Upgrade to 19.2.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Multiple vulnerabilities in the web-based management interface of Cisco SD-WAN vManage Software could allow an unauthenticated, remote attacker to conduct SQL injection attacks on an affected system. These vulnerabilities exist because the web-based management interface improperly validates values in SQL queries. An attacker could exploit these vulnerabilities by authenticating to the application and sending malicious SQL queries to an affected system. A successful exploit could allow the attacker to modify values on or return values from the underlying database or the operating system.

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

SQL injection vulnerabilities in Cisco SD-WAN vManage's web-based management interface allow unauthenticated remote attackers to inject malicious SQL queries due to improper input validation. Successful exploitation enables modification of database values or execution of operating system commands.

MitigationApply Cisco's official patches for CVE-2021-1225 immediately; restrict network access to vManage management interface and implement WAF rules as interim controls until patching is complete.

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
Sd Wan VmanageApplication
Affected:< 19.2.3

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify vManage version via CLI
    Log into the vManage CLI and run the command 'show version' or 'request software version' to retrieve the installed software version number
    Affected if The displayed version is lower than 19.2.3 (for example, 19.2.2, 19.1.x, or earlier releases)
  2. Identify vManage version via web login page
    Access the vManage web login page and check the footer or login area for the version number displayed, or capture the HTTP response headers to identify the software version
    Affected if The displayed version is lower than 19.2.3
  3. Confirm web management interface is enabled
    Verify that the vManage web-based management interface (HTTP/HTTPS on ports 443 or 8443) is running and responding. Check via 'show system inventory' or attempt a local curl to localhost on the management port
    Affected if The web interface is accessible and the version is below 19.2.3
  4. Check network exposure of management interface
    Review network access lists, firewall rules, or perform a port scan to determine if the vManage web interface is exposed to untrusted networks. Use 'show ip interface brief' on vManage to list exposed interfaces
    Affected if The management interface is reachable from outside the trusted network and the version is below 19.2.3

You are affected if your installed Cisco SD-WAN vManage version is lower than 19.2.3 and the web-based management interface is accessible.

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 19.2.3 or later
Fixed in 19.2.3
Interim mitigation

Apply Cisco's official patches for CVE-2021-1225 immediately; restrict network access to vManage management interface and implement WAF rules as interim controls until patching is complete.

Recommended fix High confidence

Cisco SD-WAN vManage version 19.2.3 or later

  1. 1. Identify current Cisco SD-WAN vManage version via the administration settings or CLI command 'show version'
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Backup the current vManage configuration using the web UI (Maintenance > Backup & Restore) or CLI
  4. 4. Download the fixed software image (version 19.2.3 or later) from Cisco.com software downloads
  5. 5. Upload the new software image to vManage via Administration > Software Manager
  6. 6. Initiate the upgrade and monitor the process for completion
  7. 7. Verify the upgrade was successful by checking the new version number
  8. 8. Confirm the vulnerability is resolved by reviewing the Cisco security advisory for CVE-2021-1225

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

Fix this in Sd Wan Vmanage Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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