Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64483: CWE-284: Improper Access Control in wazuh wazuh-dashboard-plugins

0
Medium
VulnerabilityCVE-2025-64483cvecve-2025-64483cwe-284
Published: Fri Nov 21 2025 (11/21/2025, 17:55:33 UTC)
Source: CVE Database V5
Vendor/Project: wazuh
Product: wazuh-dashboard-plugins

Description

CVE-2025-64483 is a medium severity improper access control vulnerability in Wazuh Dashboard Plugins versions 4. 9. 0 up to but not including 4. 13. 0. Authenticated users with read-only API roles can exploit this flaw to retrieve agent enrollment credentials via the /utils/configuration endpoint. These credentials allow unauthorized registration of new agents within the same Wazuh tenant without elevated UI permissions. The vulnerability does not require user interaction and can be exploited remotely over the network. It has been patched in version 4. 13.

AI-Powered Analysis

AILast updated: 02/07/2026, 08:07:01 UTC

Technical Analysis

CVE-2025-64483 is an improper access control vulnerability (CWE-284) affecting the Wazuh open source security platform, specifically its dashboard plugins component. The flaw exists in versions 4.9.0 through 4.12.x, where the Wazuh API's /utils/configuration endpoint improperly exposes agent enrollment credentials to users authenticated with read-only API roles. Normally, read-only roles should not have access to sensitive credentials or the ability to register new agents. However, due to this vulnerability, these users can retrieve enrollment credentials and use them to register new agents within the same Wazuh tenant without requiring elevated UI permissions. This unauthorized agent registration can lead to unauthorized data collection, monitoring, or manipulation within the security environment. The vulnerability is remotely exploitable over the network without user interaction and does not require elevated privileges beyond read-only API authentication. The issue was addressed and patched in Wazuh version 4.13.0. The CVSS v4.0 base score is 5.3 (medium severity), reflecting the moderate impact on confidentiality, integrity, and availability, combined with relatively low attack complexity and no need for user interaction. No known exploits have been reported in the wild as of the publication date.

Potential Impact

For European organizations, this vulnerability poses a risk of unauthorized internal reconnaissance and potential compromise of security monitoring infrastructure. Attackers with read-only API access could leverage the exposed enrollment credentials to add rogue agents, which might be used to collect sensitive data, inject false alerts, or disrupt monitoring processes. This undermines the integrity and trustworthiness of the security monitoring environment. Organizations relying on Wazuh for compliance and threat detection could face increased risk of undetected intrusions or data leakage. The impact is particularly significant for sectors with stringent compliance requirements such as finance, healthcare, and critical infrastructure, where unauthorized agent registration could lead to regulatory violations and reputational damage. Since the vulnerability requires authenticated access, insider threats or compromised credentials pose the greatest risk. However, the ease of exploitation and lack of need for user interaction increase the attack surface within affected environments.

Mitigation Recommendations

European organizations should immediately upgrade all Wazuh installations to version 4.13.0 or later, where this vulnerability is patched. Until upgrades can be performed, restrict read-only API roles strictly and audit their usage to detect any anomalous access patterns. Implement strong authentication mechanisms and rotate API credentials regularly to minimize the risk of credential compromise. Monitor API endpoint access logs, especially calls to /utils/configuration, for unauthorized attempts to retrieve enrollment credentials. Employ network segmentation to limit API access to trusted management networks and enforce least privilege principles for all users and services interacting with the Wazuh API. Additionally, conduct internal security reviews to ensure no unauthorized agents have been registered and validate the integrity of existing agents. Incorporate these checks into regular security audits and incident response plans.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-05T19:12:25.101Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6920a952e2e82c33851aa18d

Added to database: 11/21/2025, 6:02:58 PM

Last enriched: 2/7/2026, 8:07:01 AM

Last updated: 2/7/2026, 2:49:18 PM

Views: 156

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats