dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-24672

HIGH · 8.5 CVSS v3.1 Published 2025-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in codepeople Form Builder CP cp-easy-form-builder allows SQL Injection.This issue affects Form Builder CP: from n/a through <= 1.2.41.

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

SQL injection vulnerability in the Form Builder CP WordPress plugin (versions <= 1.2.41) allows injection of malicious SQL commands through unsanitized user input. The flaw enables attackers to manipulate database queries, potentially exposing sensitive data or compromising the underlying database.

MitigationUpgrade to version 1.2.42 or later which contains the patched code. If upgrade is not immediately possible, restrict access to the affected plugin endpoints at the web application firewall level.

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
None
Availability
Low

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

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. Check Form Builder CP plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate 'Form Builder CP'. Read the version number displayed beneath the plugin name. Alternatively, inspect the plugin main file header via FTP or file manager at /wp-content/plugins/form-builder-cp/ and read the Version comment.
    Affected if The version listed is 1.2.41 or lower (e.g., 1.2.40, 1.2.39, etc.)
  2. Confirm plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that the status indicator for 'Form Builder CP' shows 'Active'. A plugin must be active to be exploitable.
    Affected if The plugin shows as Active alongside a vulnerable version number.
  3. Verify exposure of form submission endpoint
    Visit your site and locate any publicly accessible form created by this plugin. The vulnerable code handles form submissions. Check if forms are reachable without authentication by visiting URLs such as /?cf_form=1 or /index.php?cf_form=1 (the exact parameter may vary based on configuration).
    Affected if Forms created by the plugin are publicly accessible and the plugin version is 1.2.41 or below.
  4. Review plugin configuration for user input fields
    In WordPress admin, go to the Form Builder CP settings and review which forms accept user-submitted data (text inputs, dropdowns, checkboxes). These fields feed into the unsanitized SQL queries described in the CVE.
    Affected if The plugin has active forms collecting user input and runs version 1.2.41 or earlier.

If the Form Builder CP plugin is active and the installed version is 1.2.41 or lower, the environment is vulnerable to CVE-2025-24672 and should be investigated further.

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

Upgrade to version 1.2.42 or later which contains the patched code. If upgrade is not immediately possible, restrict access to the affected plugin endpoints at the web application firewall level.

Recommended fix Moderate confidence

Latest version available beyond 1.2.41 (check WordPress plugin repository for current release)

  1. 1. Update the Form Builder CP (cp-easy-form-builder) plugin to the latest version available in the WordPress plugin repository
  2. 2. After updating, verify the plugin is functioning correctly by testing form creation and submission
  3. 3. Check the plugin's changelog or patchstack.com for specific fixed version details
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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