CVE-2026-119183
Deferred Deferred - Pending Action

Stored XSS in JetFormBuilder WordPress Plugin

Publication date: 2026-11-07

Last updated on: 2026-11-07

Assigner: Wordfence

Description
The JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the '<form field mapped to a post meta key, e.g. lst_cost>' parameter in all versions up to, and including, 3.6.8 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 target site to have configured a public Insert Post form writing to a post meta key and a Calculated Field whose formula references that key via the %META::key% macro, after which a single unauthenticated POST is sufficient to persist the payload.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-07
Last Modified
2026-11-07
Generated
2026-11-07
AI Q&A
2026-11-07
EPSS Evaluated
N/A
NVD
CVE-2026-119183
EUVD
EUVD-2026-119144

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
jetmonsters JetFormBuilder — Dynamic Blocks Form Builder From 0 (inc) to 3.6.8 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a Stored Cross-Site Scripting (XSS) flaw in the JetFormBuilder plugin for WordPress. It allows unauthenticated attackers to inject malicious scripts into web pages by exploiting insufficient input sanitization and output escaping in the form field mapped to a post meta key. The attack requires a public Insert Post form configured to write to a post meta key and a Calculated Field referencing that key via the %META::key% macro. A single unauthenticated POST request is enough to permanently store the malicious payload.

Detection Guidance

To detect this vulnerability, inspect WordPress sites using JetFormBuilder versions up to 3.6.8. Check for forms with mapped post meta keys and Calculated Fields referencing those keys via %META::key%. Look for unusual scripts in page content or POST requests to /wp-json/jet-form-builder/v1/handle_ajax endpoint.

Impact Analysis

This vulnerability allows attackers to inject arbitrary web scripts into pages on your WordPress site. When users access an infected page, the malicious scripts execute, potentially stealing sensitive data like cookies, session tokens, or personal information. It could also deface your site, redirect users to malicious sites, or perform actions on behalf of users without their consent.

Compliance Impact

This vulnerability could lead to data breaches, exposing user data and violating GDPR and HIPAA requirements for data protection and security. GDPR mandates strict controls to prevent unauthorized access to personal data, while HIPAA requires safeguards for protected health information. A successful exploit may result in non-compliance, legal penalties, and reputational damage.

Mitigation Strategies

Update JetFormBuilder to the latest version beyond 3.6.8. Disable public Insert Post forms writing to post meta keys if not needed. Review and remove any suspicious scripts in post meta fields. Implement strict input validation for form fields and output escaping in rendered pages.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119183. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...