CVE-2026-0626 getwpfunnels CVE debrief

Who should care

Users of the WPFunnels plugin for WordPress, particularly those with contributor level access and above, should be aware of this vulnerability and take steps to mitigate it. This includes updating the plugin to a version that fixes the vulnerability, implementing input sanitization and output escaping for the 'button_icon' parameter, monitoring for suspicious activity on the WordPress site, and restricting access to the WordPress site to only trusted users.

Technical summary

The WPFunnels plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpf_optin_form' shortcode. This is due to insufficient input sanitization and output escaping of the 'button_icon' parameter. An authenticated attacker with contributor level access and above can inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The vulnerability has a CVSS score of 6.4 and a severity of MEDIUM.

Defensive priority

Medium priority, as the vulnerability requires contributor level access and above.

Recommended defensive actions

• Update the WPFunnels plugin to a version that fixes the vulnerability
• Implement input sanitization and output escaping for the 'button_icon' parameter
• Monitor for suspicious activity on the WordPress site
• Restrict access to the WordPress site to only trusted users
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record was published on 2026-04-04T12:16:02.787Z and has not been modified since. The NVD entry is currently Deferred. There is limited information available about the vulnerability, and defenders should verify the affected scope and severity with the vendor. The WPFunnels plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'wpf_optin_form' shortcode in all versions up to, and including, 3.7.9 due to insufficient input sanitization and output escaping of the 'button_icon' parameter. 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.

Official resources