CVE-2026-14488
CriticalCVSS 9.1Exploitation Probability (EPSS)
Low risk44th percentile - higher than 44% of all known CVEs
Summary
Meta Box AIO plugin for WordPress up to 3.8.0 (with MB Frontend Submission) lacks authorization in the template_redirect dispatcher. The handle_request() function routes the mbfs_delete action without capability checks, and nonce verification is bypassed because is_ajax() returns false for template_redirect requests. Unauthenticated attackers can delete arbitrary posts and pages by supplying a post ID via the rwmb_frontend_field_object_id parameter.
Risk Assessment
An attacker can delete any content on the WordPress site, leading to data loss and site disruption.
Recommendation
Update Meta Box AIO to version 3.8.1 or later which includes the authorization fix.
Other vulnerabilities in Meta Box AIO
See all- CVE-2026-39761Critical
Unauthenticated Privilege Escalation vulnerability in Meta Box AIO versions up to 3.7.1. An attacker without authentication can gain higher privileges.
- CVE-2026-13355Critical
The Meta Box AIO plugin for WordPress is vulnerable to Privilege Escalation to Administrator in versions up to, and including, 3.11.0. This is due to a chained flaw: populate_via_query_string() unconditionally overrides the form's target object_id without authorization checks, and Form::process() lacks the user_can_edit() check, allowing unauthenticated attackers to overwrite any page's post_content with an arbitrary shortcode via wp_update_post(); the mb-user-profile component then trusts the 'role' and 'auto_login' shortcode attributes in the injected [mb_user_profile_register] shortcode without role validation. The standalone plugins Meta Box Frontend Submission (up to 4.5.6) and Meta Box User Profile (up to 3.11.0) are also affected.
Original NVD description (English source)
The Meta Box AIO plugin for WordPress is vulnerable to Missing Authorization via the template_redirect dispatcher in the MB Frontend Submission extension in versions up to, and including, 3.8.0. This is due to the handle_request() function routing the mbfs_delete action without any capability or ownership check, and the nonce verification in check_ajax() being gated behind is_ajax() which is false for template_redirect requests, making it bypassable. This makes it possible for unauthenticated attackers to delete arbitrary posts and pages by supplying an attacker-controlled post ID via the rwmb_frontend_field_object_id GET parameter on any page that hosts a frontend submission form regardless of whether allow_delete is enabled.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS