CVE-2026-0626
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WPFunnels – Easy Funnel Builder To Optimize Buyer Journeys And Get More Leads & Sales 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStored XSS vulnerability in WPFunnels WordPress plugin where the 'button_icon' parameter of the 'wpf_optin_form' shortcode lacks proper input sanitization and output escaping, allowing authenticated contributors+ to inject malicious scripts that execute when users view affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check WPFunnels plugin versionNavigate to WordPress admin > Plugins > Installed Plugins and locate WPFunnels, or inspect the plugin header file (wpfunnels.php) for the 'Version' constantAffected if Installed version is 3.7.9 or lower
-
Identify usage of wpf_optin_form shortcodeSearch WordPress database for posts containing '[wpf_optin_form' shortcode: SELECT ID, post_title FROM wp_posts WHERE post_content LIKE '%[wpf_optin_form%' AND post_status='publish'Affected if Any published content contains the wpf_optin_form shortcode
-
Inspect button_icon parameter in shortcode usageExamine the shortcode content for the button_icon attribute: SELECT ID, post_content FROM wp_posts WHERE post_content LIKE '%button_icon=%'Affected if The button_icon parameter is present and contains unescaped HTML/script tags or unusual attribute values
-
Verify output escaping statusReview plugin source code in includes/shortcodes/ directory for wpf_optin_form handler, check if button_icon attribute uses esc_attr() or similar escaping functions before outputAffected if No proper escaping (esc_attr, esc_html, esc_url) is applied to button_icon before outputting in HTML attributes
User is affected if WPFunnels version is 3.7.9 or lower AND any published content uses the wpf_optin_form shortcode with a button_icon parameter that may contain unescaped user-supplied values.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate WPFunnels plugin to version 3.8.0 or later which addresses the sanitization and escaping of the button_icon parameter.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0626 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0626 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data