CVE intelligence and bounded remediation

CVE-2025-20278 — Cisco Finesse security vulnerability

Medium CVSS 6.7

A vulnerability in the CLI of multiple Cisco Unified Communications products could allow an authenticated, local attacker to execute arbitrary commands on the underlying operating system of an affected device as the root user. This vulnerability is due to improper validation of user-supplied command arguments. An attacker could exploit this vulnerability by executing crafted commands on the CLI of an affected device. A successful exploit could allow the attacker to execute arbitrary commands on the underlying operating system of an affected device as the root user. To exploit this vulnerability, the attacker must have valid administrative credentials.

Severity
Medium
CVSS
6.7 (3.1)
Published
2025-06-04
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-77

Affected products

  • cisco / finesse / 10.5(1)
  • cisco / finesse / 10.5(1)_es1
  • cisco / finesse / 10.5(1)_es2
  • cisco / finesse / 10.5(1)_es3
  • cisco / finesse / 10.5(1)_es4
  • cisco / finesse / 10.5(1)_es5

Showing 6 representative product identities from 193 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Command, code, expression, and template injection

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace untrusted values to process execution, interpreters, evaluators, template engines, dynamic imports, and administrative scripting features.
  • Determine whether the affected path is reachable across each trust boundary and which service account or host privilege it inherits.
  • Review configuration for optional execution features, unsafe compatibility modes, and shell invocation.

Remediate safely

  • Replace string-built commands or evaluated code with fixed operations and structured argument APIs that do not invoke a shell.
  • Use strict allowlists for operation identifiers and reject unexpected input before it reaches any interpreter.
  • Update the affected component and add inert regression tests covering metacharacters, encoding variants, and alternate request paths.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.