mediumCVE-2026-9656

HubSpot All-In-One Marketing <= 11.3.62 - Authenticated (Contributor+) Sensitive Information Exposure via Block Editor Localized Script

Q: What is affected by CVE-2026-9656?

HubSpot All-In-One Marketing – Forms, Popups, Live Chat versions listed as affected should be reviewed: up to and including 11.3.62.

Q: What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

Q: How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

Q: How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.

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.

Browse WordPress security risks

ProductHubSpot All-In-One Marketing – Forms, Popups, Live Chat

CVSS4.3

EPSS0.00158

UpdatedJuly 19, 2026

Quick answer

HubSpot All-In-One Marketing – Forms, Popups, Live Chat should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

up to and including 11.3.62

Fixed versions

11.3.64

How to fix it

HubSpot All-In-One Marketing – Forms, Popups, Live Chat is affected by CVE-2026-9656, a plaintext HubSpot OAuth token exposure in the block editor. A contributor can read the refresh token and use it to access or change data in the connected HubSpot tenant. Update HubSpot All-In-One Marketing – Forms, Popups, Live Chat to 11.3.64 or a newer vendor-supported patched release. Prioritize exposed production systems and accounts that can reach the affected feature.

Inventory every HubSpot All-In-One Marketing – Forms, Popups, Live Chat deployment, version, exposed endpoint, environment, and owner.
Confirm the installed release is not an affected version up to and including 11.3.62.
Update HubSpot All-In-One Marketing – Forms, Popups, Live Chat to 11.3.64 or a newer vendor-supported patched release.
Until the update is complete, disable the plugin or block contributor access to the WordPress block editor.
Review contributor editor access, the localized leadinConfig object, unfamiliar HubSpot API clients, and unexpected HubSpot changes.
After patching, revoke and rotate the exposed HubSpot OAuth refresh token, reconnect the integration, and audit both WordPress and HubSpot.
Clear WordPress, object, page, CDN, and browser caches, then update the asset inventory and close any temporary controls only after validation.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm HubSpot All-In-One Marketing – Forms, Popups, Live Chat is on the patched version or mitigation stated above and record the exact deployed version.
Confirm contributor pages and editor scripts no longer expose a plaintext HubSpot refresh token.
Confirm the affected WordPress REST, AJAX, form, shortcode, upload, export, or admin feature is available only to the roles and requests that need it.
Review logs after remediation for continued exploit attempts or signs that the issue was used before the fix.
Rerun the relevant dependency, platform, vendor, or Fixnx security check and document the result, affected assets, change record, and cleanup evidence for CVE-2026-9656.

Related categories

WordPress Information Disclosure

Related security risks

More published guidance from the same primary category.

medium

Participants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter

Updated July 24, 2026

medium

Kirki <= 6.0.14 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'context' Parameter

Updated July 24, 2026

medium

CVE-2026-65475 Modula Image Gallery vulnerability

Updated July 24, 2026

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-9656?

HubSpot All-In-One Marketing – Forms, Popups, Live Chat versions listed as affected should be reviewed: up to and including 11.3.62.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.