dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-49778

HIGH · 7.1 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Unauthenticated Cross Site Scripting (XSS) in WPFunnels Pro <= 2.9.4 versions.

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 · moderate confidence

Unauthenticated Cross Site Scripting (XSS) vulnerability in WPFunnels Pro WordPress plugin affecting versions 2.9.4 and below. An unauthenticated attacker can inject malicious JavaScript scripts into web pages served by the plugin, potentially stealing session cookies, credentials, or performing actions on behalf of authenticated users.

MitigationUpdate WPFunnels Pro to a version newer than 2.9.4 once the vendor releases a patch, or remove the plugin if no patch is available.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WPFunnels Pro is installed
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and search for 'WPFunnels Pro' in the list of active plugins
    Affected if WPFunnels Pro appears in the installed plugins list
  2. Identify the installed version
    In the Plugins list, click on WPFunnels Pro to view the plugin details, or open the main plugin PHP file (usually wpfunnels-pro.php) and locate the version number in the file header comment
    Affected if version displayed is 2.9.4 or lower
  3. Verify the plugin is active
    In the WordPress Plugins list, confirm that WPFunnels Pro shows as 'Active' under the plugin status column
    Affected if plugin status is Active

The environment is affected if WPFunnels Pro is installed, active, and running version 2.9.4 or lower, since the vulnerability is unauthenticated and applies to all pages served by the vulnerable plugin version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WPFunnels Pro to a version newer than 2.9.4 once the vendor releases a patch, or remove the plugin if no patch is available.

Recommended fix High confidence

WPFunnels Pro version higher than 2.9.4 (e.g., 2.9.5 or latest available)

  1. Check your current WPFunnels Pro version in WordPress admin under Plugins
  2. If the installed version is 2.9.4 or lower, navigate to Plugins > Add New > Upload Plugin (or use WordPress plugin repository if available)
  3. Upload and install the latest version of WPFunnels Pro (version higher than 2.9.4)
  4. After installation, verify the new version number in Plugins list
  5. Clear any caching plugins or server-side caches
  6. Test that the plugin functionality works correctly after upgrade
Caveat Review plugin changelog for any breaking changes between your current version and the upgrade version before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-49778 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-49778 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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