JetFormBuilder Stripe Gateway inserts an unescaped payment token into SQL
An unauthenticated caller can supply a payment token that is used in an SQL statement without adequate sanitization or escaping. Attacker-controlled token data can alter the query and expose database contents, including password hashes. The payment endpoint and token parameter name are unspecified. Affected versions: < 1.1.0. Confirmed fixed release: 1.1.0.
- Component
- jet-form-builder-stripe-gateway
- Plugin slug
jet-form-builder-stripe-gateway- Affected
- < 1.1.0
- Safe version
1.1.0- Published
- Sep 23, 2026
This CVE was published Sep 23, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update to 1.1.0 or later, preferably the current supported release. Use parameterized queries for payment tokens, validate token format before database access and review exposed credentials if exploitation is suspected.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The jet-form-builder-stripe-gateway WordPress plugin before 1.1.0 does not sanitise and escape a payment token before using it in a SQL statement, allowing unauthenticated users to extract arbitrary data from the database, including password hashes.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N