WatchGuard AP Authenticated Command Injection in Diagnostic CLI

Why this deserves its current priority

CVSS is 8.6. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps WatchGuard/WatchGuard AP (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for WatchGuard/WatchGuard AP.
2. 2Review the reported fix. Source-reported solution: WatchGuard AP 3.4.8

Evidence timeline and material changes

1. Published upstream

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Sep 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Sep 28, 2026

Sources and claim methodology

• Source referencepsirt.watchguard.com

Related CVEs

• WatchGuard AP Improper Access Control in API Service Allows Unauthenticated AccessSame watchguard/watchguard ap package
• WatchGuard AP Command Injection in Internal Management API Allows Command ExecutionSame watchguard/watchguard ap package
• FreePBX: Authenticated Remote Code Execution in FreePBX Music on Hold (MoH) ModuleAlso CWE-78
• Authenticated Command Injection in FreePBX UCP InterfaceAlso CWE-78
• Token Optimizer MCP: OS command injection in smart_user via username in get-user-infoAlso CWE-78
• FreePBX: Authenticated API generatedocs Host Command InjectionAlso CWE-78