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-66146: CWE-862 Missing Authorization in merkulove Logger for Elementor

0
Medium
VulnerabilityCVE-2025-66146cvecve-2025-66146cwe-862
Published: Wed Dec 31 2025 (12/31/2025, 19:50:21 UTC)
Source: CVE Database V5
Vendor/Project: merkulove
Product: Logger for Elementor

Description

Missing Authorization vulnerability in merkulove Logger for Elementor allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Logger for Elementor: from n/a through 1.0.9.

AI-Powered Analysis

AILast updated: 12/31/2025, 20:14:18 UTC

Technical Analysis

CVE-2025-66146 is a Missing Authorization vulnerability classified under CWE-862 affecting the merkulove Logger for Elementor plugin, versions up to 1.0.9. This vulnerability stems from improperly configured access control mechanisms within the plugin, which fail to adequately restrict certain operations to authorized users only. As a result, users with limited privileges (PR:L) can exploit this flaw to perform unauthorized actions that can alter data integrity or disrupt service availability. The vulnerability does not require user interaction (UI:N) and can be exploited remotely over the network (AV:N). The CVSS v3.1 base score is 5.4, reflecting a medium severity level due to the combination of low attack complexity (AC:L), partial privileges required, and impacts on integrity and availability but no confidentiality loss. No patches are currently linked, and no known exploits have been reported in the wild, indicating that the vulnerability is either newly disclosed or not yet weaponized. The plugin is used as an extension for Elementor, a popular WordPress page builder, which means the attack surface includes WordPress sites using this plugin. Attackers exploiting this vulnerability could manipulate logs or other plugin-related data, potentially leading to unauthorized changes or denial of service conditions. The vulnerability highlights the importance of rigorous access control enforcement in WordPress plugins, especially those handling logging or administrative functions.

Potential Impact

For European organizations, this vulnerability poses a moderate risk primarily to the integrity and availability of their WordPress-based websites and services. Unauthorized users with limited privileges could exploit the missing authorization to alter or delete log data, potentially covering tracks of malicious activity or disrupting monitoring capabilities. This could hinder incident response and forensic investigations. Additionally, if the plugin controls or influences other site functionalities, unauthorized changes could lead to service disruptions or degraded user experience. Organizations relying on the affected plugin for compliance or auditing purposes may face regulatory risks if logs are tampered with. The impact is heightened in sectors where website integrity and availability are critical, such as e-commerce, finance, healthcare, and government services. Since the vulnerability does not affect confidentiality directly, the risk of data breaches is lower, but the potential for operational disruption remains significant. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation.

Mitigation Recommendations

1. Immediately review and restrict user privileges within WordPress to ensure that only trusted users have access to functions related to the Logger for Elementor plugin. 2. Monitor WordPress user activity and plugin logs for unusual or unauthorized actions that could indicate exploitation attempts. 3. Apply vendor patches or updates as soon as they become available; maintain communication with the plugin vendor for timely security updates. 4. Consider temporarily disabling the Logger for Elementor plugin if it is not essential or if a patch is not yet available, to reduce attack surface. 5. Implement web application firewalls (WAF) with rules tailored to detect and block suspicious requests targeting the plugin endpoints. 6. Conduct regular security audits and penetration testing focusing on WordPress plugins and their access control mechanisms. 7. Educate site administrators about the risks of privilege escalation and the importance of least privilege principles. 8. Use multi-factor authentication (MFA) for administrative accounts to reduce the risk of compromised credentials being used to exploit the vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-11-21T11:23:07.863Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6955807ddb813ff03efdb3fa

Added to database: 12/31/2025, 7:58:53 PM

Last enriched: 12/31/2025, 8:14:18 PM

Last updated: 1/7/2026, 4:12:38 AM

Views: 45

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