CVE-2025-15616: Wazuh Agent and Manager OS Command Injection and Untrusted Search Path
Wazuh wazuh-agent and wazuh-manager versions 2.1.0 before 4.8.0 contain multiple shell injection and untrusted search path vulnerabilities that allow attackers to execute arbitrary commands through various components including logcollector configuration, maild SMTP server tags, and Kaspersky AR script parameters. Attackers can exploit these vulnerabilities by injecting malicious commands through configuration files, SMTP server settings, and custom flags to achieve remote code execution on affected systems.
Security readout for executives and security teams
Plain-English summary
This CVE describes command execution flaws in Wazuh agent and manager before 4.8.0. A highly privileged attacker could abuse configuration-related inputs to run arbitrary commands on affected systems. Treat it seriously because Wazuh often has broad visibility and trusted access across monitored environments.
Executive priority
Prioritize remediation where Wazuh manages sensitive servers, has elevated permissions, or is administered by many users. This is high priority but not currently supported as known exploited by the provided sources.
Technical view
The bundle describes multiple shell injection and untrusted search path issues in Wazuh logcollector configuration, maild SMTP server tags, and Kaspersky AR script parameters. CVSS 4.0 is 7.1 with network attack vector, low complexity, no user interaction, and high privileges required.
Likely exposure
Organizations running Wazuh agent or manager versions from 2.1.0 before 4.8.0 may be exposed. Exact exposure depends on deployed components, enabled integrations, and who can modify relevant configuration or SMTP settings.
Exploitation context
The source bundle does not indicate CISA KEV listing or active exploitation. The CVSS vector indicates high privileges are required, reducing opportunistic risk but leaving meaningful insider, compromised-admin, or post-compromise escalation concerns.
Researcher notes
Version evidence should be cross-checked against the vendor advisory because the bundle’s structured affected entries are narrower than the description. Avoid assuming exploitation in the wild. Focus validation on privileged configuration paths and affected Wazuh components.
Mitigation direction
Upgrade Wazuh agent and manager to version 4.8.0 or later.
Review the Wazuh advisory for component-specific fixed versions and packages.
Restrict administrative access to Wazuh configuration and SMTP settings.
Audit custom active response scripts and third-party integration parameters.
Monitor Wazuh hosts for unexpected child processes or command execution.
Validation and detection
Inventory all Wazuh agent and manager versions across the environment.
Confirm no deployed instance is below version 4.8.0.
Identify systems using logcollector, maild SMTP tags, or Kaspersky AR parameters.
Review recent configuration changes by privileged Wazuh users.
Check endpoint telemetry for unusual Wazuh-spawned processes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.