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

CVE-2026-54195

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 JetFormBuilder <= 3.6.0.1 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

An unauthenticated cross-site scripting (XSS) vulnerability exists in JetFormBuilder plugin versions 3.6.0.1 and below. The vulnerability allows attackers to inject malicious JavaScript code through form inputs that are not properly sanitized before being rendered in the application's output.

MitigationUpdate JetFormBuilder to a version newer than 3.6.0.1. If immediate updating is not possible, disable the plugin until a patch can be applied.

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. Verify JetFormBuilder plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'JetFormBuilder' in the list, or check the wp-content/plugins/jetformbuilder directory exists
    Affected if JetFormBuilder is present in the plugins directory
  2. Check installed JetFormBuilder version
    Navigate to Plugins > Installed Plugins > JetFormBuilder and read the version number displayed under the plugin name, or inspect the main plugin file header for the Version field
    Affected if The version is 3.6.0.1 or lower
  3. Confirm JetFormBuilder forms are in use
    Go to JetFormBuilder > Forms in the WordPress admin panel and verify that at least one form exists and is published
    Affected if Active forms exist and are embedded on the site
  4. Check if form submissions are displayed publicly
    Review the site's published pages and posts that contain JetFormBuilder forms to see if submitted data is rendered back to users (such as in submission confirmations, user dashboards, or frontend submission displays)
    Affected if Form submissions or user input are rendered to visitors without server-side output encoding

You are affected if JetFormBuilder version 3.6.0.1 or below is installed AND your site publishes forms that display user-submitted data to visitors.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetFormBuilder to a version newer than 3.6.0.1. If immediate updating is not possible, disable the plugin until a patch can be applied.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54195 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54195 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