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.
Published: 2026-09-23
Score: 8.6 High
EPSS: < 1% Very Low
KEV: No
Impact: Data Exposure
Action: Apply Patch
AI Analysis

Impact

An unauthenticated blind SQL injection flaw exists in the JetFormBuilder Stripe Gateway WordPress plugin before version 1.1.0. Unsanitised payment tokens are incorporated directly into a SQL query, allowing attackers to extract arbitrary data, including password hashes. The weakness corresponds to CWE‑89, reflecting SQL injection. The primary impact is the compromise of sensitive database contents, potentially exposing credentials and other confidential information, which could lead to account takeovers or further lateral movement.

Affected Systems

Any installation of the JetFormBuilder Stripe Gateway WordPress plugin older than version 1.1.0 is affected. The vulnerability does not require special user privileges; it is triggered by unauthenticated access to the payment‑token handling endpoint.

Risk and Exploitability

The CVSS score of 8.6 classifies this flaw as High severity. EPSS is not available, so the exploitation probability is unknown, and the vulnerability is not listed in the CISA KEV catalog. The likely attack vector is an unauthenticated HTTP request to the payment‑token endpoint where the token value is inserted into a SQL statement without escaping. Exploit requires no local privilege and could be performed remotely by any user. Due to the lack of a publicly known exploit and the high potential impact, the risk is considered significant in environments that rely on this plugin for payment processing.

Generated by OpenCVE AI on September 23, 2026 at 14:02 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the JetFormBuilder Stripe Gateway plugin to version 1.1.0 or later, which corrects the unsanitised payment‑token handling.
  • Implement web‑application firewall rules or WAF filters to block suspicious SQL injection patterns that target the payment‑token parameter.
  • Restrict unauthenticated access to the payment‑token processing endpoint, for example by enforcing authentication or by limiting the route to privileged users only.

Generated by OpenCVE AI on September 23, 2026 at 14:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 23 Sep 2026 11:45:00 +0000

Type Values Removed Values Added
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.
Title JetFormBuilder Stripe Gateway < 1.1.0 - Unauthenticated Blind SQLi via Payment Token
Weaknesses CWE-89
References
Metrics cvssV3_1

{'score': 8.6, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N'}

ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-09-23T11:01:49.140Z

Reserved: 2026-09-18T11:56:35.176Z

Link: CVE-2022-4997

cve-icon Vulnrichment

Updated: 2026-09-23T10:40:01.980Z

cve-icon NVD

Status : Received

Published: 2026-09-23T06:16:59.060

Modified: 2026-09-23T11:17:08.480

Link: CVE-2022-4997

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-09-23T14:15:06Z

Weaknesses
  • CWE-89

    Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')