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

CVE-2026-11767

HIGH · 8.8 CVSS v3.1 Published 2026-07-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges 4 weeks old

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
The Free Builder for Elementor WordPress plugin before 1.6.7 does not sanitise submitted contact form field values before storing them and outputting them in the admin dashboard, allowing unauthenticated attackers to perform Stored Cross-Site Scripting attacks that execute when a logged-in administrator views the form submissions.

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 confidence

The Free Builder for Elementor WordPress plugin before version 1.6.7 contains a stored Cross-Site Scripting vulnerability. Unauthenticated attackers can submit malicious JavaScript code through contact form fields, which gets stored without sanitization. When administrators view form submissions in the admin dashboard, the unsanitized output causes the stored XSS payload to execute in their browser session.

MitigationUpdate the Free Builder for Elementor plugin to version 1.6.7 or later to obtain the fix for proper input sanitization and output encoding.

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 Free Builder for Elementor plugin is installed
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or inspect the plugin directory at wp-content/plugins/free-builder-for-elementor/ for the main PHP file to verify the plugin exists
    Affected if The plugin directory or plugin list shows Free Builder for Elementor is active on the site
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find the Free Builder for Elementor entry to read the version number displayed
    Affected if The displayed version is lower than 1.6.7 (for example 1.6.6, 1.6.5, or earlier)
  3. Verify contact form functionality is in use
    Check if any pages or templates have the Free Builder contact form widget/module embedded, or query the database for form-related post meta entries
    Affected if The plugin's contact form widget is actively published on the site and accepting submissions
  4. Inspect stored form submission data
    Query the WordPress database (typically wp_postmeta table) for entries related to the plugin's form submissions using a pattern like meta_key containing 'free_builder' or 'form_submission'
    Affected if Form submission records exist in the database containing the unsanitized field data
  5. Check admin access to submission data
    Navigate to the WordPress admin dashboard area where Free Builder form submissions are displayed (usually under the plugin's menu or under Comments/Entries)
    Affected if Admin users have access to view stored form submissions - the XSS executes when an administrator views these entries in the dashboard

A site is affected if Free Builder for Elementor plugin version is below 1.6.7 AND the contact form feature is actively used with stored submissions that admins can view in the dashboard.

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 the Free Builder for Elementor plugin to version 1.6.7 or later to obtain the fix for proper input sanitization and output encoding.

Recommended fix High confidence

Free Builder for Elementor version 1.6.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Free Builder for Elementor' in the plugin list
  4. If an update is available, click 'Update Now' to update to version 1.6.7 or later
  5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org
  6. After updating, verify the installed version is 1.6.7 or higher under Plugins > Installed Plugins
  7. Review any existing contact form submissions in the plugin's submissions area and delete any suspicious entries containing script tags or unusual HTML

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
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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