dbcve.org
JetformbuilderWordPress extension · Crocoblock

CVE-2023-33212

HIGH · 8.8 CVSS v3.1 Published 2023-05-28
Fix available
A fix is available. Upgrade to 3.0.7 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Crocoblock JetFormBuilder — Dynamic Blocks Form Builder plugin <= 3.0.6 versions.

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

Cross-Site Request Forgery (CSRF) vulnerability in the JetFormBuilder WordPress plugin versions 3.0.6 and below. CSRF attacks trick authenticated users into unknowingly submitting malicious requests, potentially allowing attackers to perform unauthorized actions on behalf of victim users.

MitigationImplement anti-CSRF tokens (nonce validation) on all form submissions and state-changing operations within the plugin, and ensure proper referer validation. Users should update to a patched version when available.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
JetformbuilderWordPress extension
Affected:< 3.0.7

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'JetFormBuilder' or 'Crocoblock Jetformbuilder' in the list. Note whether it is active or inactive.
    Affected if The plugin is installed and active (inactive plugins are not vulnerable to CSRF exploits in the same way, but the vulnerable code is still present)
  2. Check installed JetFormBuilder version
    In the plugins list, find JetFormBuilder and note the version number displayed, or look in the plugin's main file header. Compare this version against the affected range: versions 3.0.6 and below are vulnerable.
    Affected if Installed version is 3.0.6 or lower (the vulnerability exists in versions below 3.0.7)
  3. Identify active JetFormBuilder forms
    In WordPress admin, navigate to JetFormBuilder > Forms (or check Pages > All Pages for any forms created with the plugin). Determine if any forms are published and accessible on the site.
    Affected if Any JetFormBuilder forms are published and accessible; CSRF exploits require a targeted form to be present on the site
  4. Audit form handlers for nonce validation
    Examine the plugin's form submission handling code (typically in includes/actions/*.php or similar). Look for the presence of 'wp_verify_nonce', 'check_admin_referer', or 'check_ajax_referer' calls on form action handlers that process state-changing requests.
    Affected if Form action handlers lack proper nonce validation checks, confirming the CSRF vulnerability is present in the code

A site is affected if JetFormBuilder version 3.0.6 or lower is active and any JetFormBuilder forms are in use on the site.

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
Upgrade available Upgrade to 3.0.7 or later
Fixed in 3.0.7
Interim mitigation

Implement anti-CSRF tokens (nonce validation) on all form submissions and state-changing operations within the plugin, and ensure proper referer validation. Users should update to a patched version when available.

Recommended fix High confidence

JetFormBuilder version 3.0.7 or later

  1. Log into the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate JetFormBuilder in the plugin list
  4. Check if current version is less than 3.0.7
  5. If vulnerable, click 'Update Now' on JetFormBuilder to update to version 3.0.7 or latest available version
  6. Verify the update completed successfully and the plugin shows version 3.0.7 or higher

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

Fix this in Jetformbuilder Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-33212 — 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-2023-33212 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