CVE-2026-111317 · Package
NO FIX YET · SEE WHAT TO DO
The JetFormBuilder WordPress plugin does not sanitize or escape form field values, so an unauthenticated visitor can store a script in a form submission. The script runs in the browser of a privileged user who opens the affected form page.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the JetFormBuilder plugin up to and including 3.6.7 that have a form with both the Save Form Record action and a Form Record preset enabled. Exposure needs a privileged user to open the front-end form page with the preset's record query variable set to the attacker's record ID. Sites without that form configuration, or without the plugin, can skip it.
Not affected if no-save-form-record-preset, plugin-above-3.6.7, plugin-not-installed
Who cares jetformbuilder, self-hosted, wordpress
3.6.7 are listed as affected.3.6.7 (fixed version not stated in the sources).The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<any form field name — e.g. 'payload'>' parameter in all versions up to, and including, 3.6.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires the targeted form to have both the Save Form Record action enabled and a form-level Form Record preset configured; the stored payload only executes when a privileged user visits the front-end form page with the preset's record query variable set to the attacker's submitted record ID.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.