WordPress security changelog
MEDIUM CVE-2026-9656 Deferred

HubSpot All-In-One Marketing – Forms, Popups, Live Chat: Sensitive information exposure

HubSpot All-In-One Marketing – Forms, Popups, Live Chat is affected by sensitive information exposure. Exploitation requires at least contributor-level access. Successful exploitation can disclose data that should not be available to the caller. The published affected range is <= 11.3.62.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
HubSpot All-In-One Marketing – Forms, Popups, Live Chat
Plugin slug
leadin
Affected
<= 11.3.62
Safe version
> 11.3.62
Published
Jul 17, 2026
Weakness
CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor

This CVE was published Jul 17, 2026 and is one of 4 known issues for this plugin.

What to do

Update, patch or deactivate.

Update HubSpot All-In-One Marketing – Forms, Popups, Live Chat to a release after 11.3.62, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

The HubSpot All-In-One Marketing – Forms, Popups, Live Chat plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 11.3.62 via the wp_localize_script() / window.leadinConfig JavaScript object. This makes it possible for authenticated attackers, with contributor-level access and above, to extract the site's plaintext HubSpot OAuth refresh token exposed via the window.leadinConfig JavaScript object, which can then be used to access or modify data in the connected HubSpot tenant. Although the refresh token is stored at rest with AES-256-CTR encryption, decryption occurs server-side before the plaintext value is passed to wp_localize_script(), rendering the at-rest encryption ineffective against this exposure path.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

Primary and upstream sources