dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-32525

CRITICAL · 9.9 CVSS v3.1 Published 2026-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Control of Generation of Code ('Code Injection') vulnerability in jetmonsters JetFormBuilder jetformbuilder allows Code Injection.This issue affects JetFormBuilder: from n/a through <= 3.5.6.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Code injection vulnerability in JetFormBuilder WordPress plugin (versions <=3.5.6.1) allows remote attackers to inject and execute arbitrary code, likely through unsanitized input in form handling or dynamic code generation functions.

MitigationUpdate JetFormBuilder to the latest available version immediately; if no patched version exists, disable the plugin and implement WAF rules to block suspicious form submission patterns until a fix is released.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify JetFormBuilder plugin installation and version
    Navigate to WordPress admin > Plugins > Installed Plugins, locate JetFormBuilder, and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/jetformbuilder/readme.txt or the main plugin file for the Version: field.
    Affected if The installed version is 3.5.6.1 or any earlier version (the vulnerability affects versions through 3.5.6.1).
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify that JetFormBuilder shows as 'Active' under the plugin status.
    Affected if The plugin is active and processing form submissions, enabling the injection vector.
  3. Identify publicly accessible forms using JetFormBuilder
    Review all published forms on the site that were created with JetFormBuilder. Check the form settings to see if form actions include any code generation features (such as custom code actions, dynamic field population from PHP, or webhook/data processing that executes server-side code).
    Affected if Forms with actions that trigger eval(), call_user_func(), include/require on user-submitted data are present and publicly accessible.
  4. Inspect form submission handling for unsafe functions
    If you have file access, examine the jetformbuilder plugin files in wp-content/plugins/jetformbuilder, specifically looking for form processing handlers that use eval(), call_user_func(), or dynamic includes that incorporate user input without sanitization.
    Affected if The plugin code contains unsafe function calls processing form data without proper sanitization.

You are affected if JetFormBuilder version 3.5.6.1 or earlier is installed and active, with forms that can submit data to server-side code generation functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update JetFormBuilder to the latest available version immediately; if no patched version exists, disable the plugin and implement WAF rules to block suspicious form submission patterns until a fix is released.

Recommended fix Moderate confidence

Latest available version of JetFormBuilder (check WordPress plugin repository for post-3.5.6.1 release with security fix)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate JetFormBuilder in the plugin list
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, clear any caching plugins or server-side caches
  6. 6. Verify the plugin is functioning correctly by testing form submissions
  7. 7. Review JetFormBuilder's changelog or the WordPress plugin repository for the specific fixed version number
Caveat Standard WordPress plugin update precautions apply - backup site before updating

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32525 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32525 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data