What is the CVSS score of CVE-2026-11597?

CVE-2026-11597 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

Surbma Infusionsoft Shortcode CVE-2026-11597

EUVD-2026-39956 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-06-27 Wordfence

GHSA-7wpj-grc3-jrwm

WordPress XSS Wordpress Plugin Surbma Infusionsoft Shortcode Surbma

6.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.4 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

vuln.today AI

5.4 MEDIUM

Stored XSS requires a victim to visit the injected page (UI:R); contributor authentication required (PR:L); scope changes to victim browser (S:C); no availability impact.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 27, 2026 - 07:54 vuln.today

CVE Published

Jun 27, 2026 - 06:50 cve.org

MEDIUM 6.4

DescriptionCVE.org

The Surbma | Infusionsoft Shortcode plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'infusionsoft-form' shortcode in versions up to, and including, 2.0.1. This is due to insufficient input sanitization and output escaping on user-supplied 'account' and 'id' shortcode attributes in the surbma_infusionsoft_shortcode_shortcode() function, which are concatenated directly into a <script> tag's src attribute. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

AnalysisAI

Stored Cross-Site Scripting in the Surbma | Infusionsoft Shortcode WordPress plugin (versions ≤ 2.0.1) allows authenticated contributors to inject persistent malicious scripts that execute in any visitor's browser. The flaw originates in the surbma_infusionsoft_shortcode_shortcode() function, where the 'account' and 'id' shortcode attributes are concatenated without sanitization directly into a <script> tag's src attribute - a particularly dangerous injection point because it bypasses many output-escaping checks that target HTML attribute or element contexts. No public exploit code has been identified at time of analysis, and no CISA KEV listing is present.

Technical ContextAI

The affected code is a WordPress shortcode handler plugin designed to embed Infusionsoft (now Keap) web forms via a <script> tag whose src URL is dynamically built from user-supplied shortcode attributes. CWE-79 (Improper Neutralization of Input During Web Page Generation - XSS) applies: the root cause is that the 'account' and 'id' parameters passed to [infusionsoft-form] are passed through the surbma_infusionsoft_shortcode_shortcode() function and written verbatim into a <script src='...'> tag in generated page HTML, with no escaping or allowlist validation. Because the injection point is a script src attribute, an attacker can point it to an attacker-controlled domain delivering arbitrary JavaScript rather than the intended Infusionsoft snippet. The CPE identifier is cpe:2.3:a:surbma:surbma_|_infusionsoft_shortcode:*:*:*:*:*:*:*:*, covering all versions through 2.0.1. Affected code lines are documented at the WordPress plugin trac repository at lines 31 and 35 of the 2.0 tag.

RemediationAI

Upstream fix commits are documented in the WordPress plugin trac changesets referenced in the CVE record, indicating the vulnerability has been addressed in a post-2.0.1 release; however, an exact patched version number is not independently confirmed from the available data - check the WordPress.org plugin page for the latest release and apply it immediately. As an interim workaround, site administrators should revoke or audit contributor-level accounts to prevent untrusted users from inserting the [infusionsoft-form] shortcode, or disable the plugin entirely until a verified patched version is installed. The WordPress Content Security Policy (CSP) header, if configured to block inline and dynamic script sources, would mitigate the impact of the injected script src but does not remove the root cause. Note that restricting contributor access may affect legitimate editorial workflows.