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-12170: CWE-862 Missing Authorization in bandido Checkbox

0
Medium
VulnerabilityCVE-2025-12170cvecve-2025-12170cwe-862
Published: Fri Nov 21 2025 (11/21/2025, 07:31:47 UTC)
Source: CVE Database V5
Vendor/Project: bandido
Product: Checkbox

Description

The Checkbox plugin for WordPress is vulnerable to unauthorized loss of data due to a missing capability check on the 'wp_ajax_nopriv_checkbox_clean_log' AJAX endpoint in all versions up to, and including, 2.8.10. This makes it possible for unauthenticated attackers to clear log files.

AI-Powered Analysis

AILast updated: 11/21/2025, 08:41:50 UTC

Technical Analysis

CVE-2025-12170 is a vulnerability classified under CWE-862 (Missing Authorization) found in the Checkbox plugin for WordPress, developed by bandido. The flaw exists in the AJAX endpoint 'wp_ajax_nopriv_checkbox_clean_log', which lacks proper capability checks to verify if the requester is authorized to perform log cleaning operations. This endpoint is accessible without authentication (as indicated by 'nopriv'), enabling any unauthenticated attacker to invoke it and clear log files maintained by the plugin. The affected versions include all versions up to and including 2.8.10. The vulnerability does not allow attackers to read or modify other data, nor does it affect availability of the site, but it compromises the integrity of log data by allowing unauthorized deletion. This can severely impact incident response and forensic analysis since logs are critical for tracking malicious activity and troubleshooting. The CVSS v3.1 base score is 5.3 (medium), reflecting network attack vector, low attack complexity, no privileges required, no user interaction, and impact limited to integrity loss of logs only. No patches or exploits are currently reported, but the lack of authorization checks represents a significant security oversight. The vulnerability is relevant for any WordPress site using the Checkbox plugin, which is a popular form and survey plugin, often deployed in European organizations for customer feedback, registrations, and data collection.

Potential Impact

For European organizations, this vulnerability poses a risk primarily to the integrity of security and operational logs. Unauthorized clearing of logs can obscure evidence of malicious activity, complicate incident investigations, and delay detection of breaches. This is particularly critical for organizations subject to strict regulatory requirements such as GDPR, which mandates maintaining accurate records and audit trails. Loss of logs could lead to non-compliance penalties and undermine trust in security controls. While the vulnerability does not directly compromise user data confidentiality or site availability, the indirect impact on security monitoring and forensic capabilities can be significant. Organizations relying on the Checkbox plugin for critical forms or data collection may also face operational risks if logs used for troubleshooting or analytics are erased. The ease of exploitation (no authentication or user interaction required) increases the likelihood of opportunistic attacks, especially on publicly accessible WordPress sites. Therefore, European entities with public-facing WordPress installations using this plugin should consider this vulnerability a moderate threat to their security posture.

Mitigation Recommendations

1. Immediate mitigation should involve restricting access to the vulnerable AJAX endpoint by implementing server-level access controls such as IP whitelisting or web application firewall (WAF) rules to block unauthorized requests to 'wp_ajax_nopriv_checkbox_clean_log'. 2. Update the Checkbox plugin to a patched version once available from the vendor, ensuring that proper capability checks are enforced on all AJAX endpoints. 3. In the absence of an official patch, consider applying custom code fixes or disabling the vulnerable AJAX action via WordPress hooks to prevent unauthorized log clearing. 4. Enhance logging and monitoring to detect unusual or repeated requests to the affected endpoint, which may indicate exploitation attempts. 5. Regularly back up log files and store them securely offsite to preserve forensic data in case of tampering. 6. Conduct security audits of all WordPress plugins to identify and remediate similar missing authorization issues. 7. Educate site administrators on the importance of plugin updates and monitoring for suspicious activity. These steps go beyond generic advice by focusing on immediate access restrictions, custom code mitigation, and forensic readiness.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-10-24T14:33:23.895Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6920235bcf2d47c38997b534

Added to database: 11/21/2025, 8:31:23 AM

Last enriched: 11/21/2025, 8:41:50 AM

Last updated: 11/22/2025, 7:57:12 AM

Views: 7

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats