CVE-2025-11991
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 · uneditedThe JetFormBuilder — Dynamic Blocks Form Builder plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the run_callback function in all versions up to, and including, 3.5.3. This makes it possible for unauthenticated attackers to generate forms using AI, consuming site's AI usage limits.
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 · high confidenceJetFormBuilder plugin has a missing capability check on the run_callback function, allowing unauthenticated attackers to invoke AI form generation features. This results in unauthorized consumption of the site's AI API quota and potential denial of service through resource exhaustion.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify JetFormBuilder plugin versionNavigate to Plugins > Installed Plugins in the WordPress admin dashboard and locate JetFormBuilder. The version number is displayed beneath the plugin name.Affected if The installed version is lower than 3.5.4 (the version that includes the capability check fix).
-
Confirm AI features are enabledGo to JetFormBuilder > Settings (or similar AI configuration area) and check whether any AI form generation or AI-related features have been activated or configured.Affected if AI features or AI form generation settings are turned on, making the vulnerable callback function accessible.
-
Review server access logs for callback requestsExamine web server access logs (typically in /var/log/nginx/access.log or /var/log/apache2/access.log) for requests to endpoints containing 'run_callback', 'ai_callback', or similar JetFormBuilder callback paths.Affected if Unauthenticated requests (those without valid WordPress user authentication) are present in the logs targeting callback functions.
A user is affected if their JetFormBuilder version is below 3.5.4 AND AI features are enabled, as this allows unauthenticated attackers to trigger AI form generation through the vulnerable run_callback function.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate to version 3.5.4 or later which includes the missing capability check on the run_callback function. If no update is available, consider temporarily disabling AI-related features or implementing a WAF rule to block unauthorized callback requests.
Upgrade to JetFormBuilder version 3.5.4 or later (the first version containing the security fix)
- 1. Log in to the WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate JetFormBuilder — Dynamic Blocks Form Builder in the plugin list
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. Alternatively, download the latest version from the WordPress plugin repository and upload it manually
- 6. After updating, verify that the run_callback function now requires proper authorization/capability checks
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-11991 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-11991 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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