CVE-2026-11767 Free Theme Builder for Elementor vulnerability
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.
Browse WordPress security risksQuick answer
CRThemes Free Theme Builder for Elementor should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- < 1.6.7
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
CVE-2026-11767 affects Free Theme Builder for Elementor and involves cross-site scripting. Successful exploitation may run attacker-controlled script in a trusted user's browser and expose session or application data. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Upgrade Free Theme Builder for Elementor to 1.6.7 or later.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses Free Theme Builder for Elementor.
- Compare the installed version with the recorded affected range: < 1.6.7.
- Upgrade Free Theme Builder for Elementor to 1.6.7 or later.
- Until patched, disable the affected Free Theme Builder for Elementor feature or plugin and restrict its public and administrator endpoints.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to Free Theme Builder for Elementor; remove access that is not required.
- Review submissions, stored content, administrator activity, CSP reports, and web logs for script payloads or suspicious browser requests.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-11767 in place.
- Use a safe regression test to confirm the affected cross-site scripting path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
CVE-2026-65475 Modula Image Gallery vulnerability
Updated July 24, 2026
highCVE-2026-65511 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
mediumCVE-2026-65522 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
Trusted references
FAQ
What is affected by CVE-2026-11767?
CRThemes Free Theme Builder for Elementor versions listed as affected should be reviewed: < 1.6.7.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.