CVE-2025-24773
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 · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in mojoomla WPCRM - CRM for Contact form CF7 & WooCommerce wpcrm allows SQL Injection.This issue affects WPCRM - CRM for Contact form CF7 & WooCommerce: from n/a through <= 3.2.0.
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 confidenceSQL injection vulnerability in the WPCRM plugin for WordPress allows attackers to inject malicious SQL commands through unsanitized input. The flaw affects version 3.2.0 and below, potentially enabling database compromise, data exfiltration, or administrative access.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify WPCRM plugin is installedLog into WordPress admin dashboard, navigate to Plugins > Installed Plugins, and locate the WPCRM plugin in the list. Note whether it is active or inactive.Affected if WPCRM plugin is installed and active on the WordPress site
-
Check installed WPCRM versionIn the Plugins list, click on the plugin name or view the plugin details to display the installed version number. Compare this to the affected range of 3.2.0 and below.Affected if Installed version is 3.2.0 or lower
-
Inspect database query handlingAccess the WPCRM plugin files via FTP or file manager. Locate PHP files that handle database queries (typically in the main plugin file or classes folder). Search for direct SQL query construction using $wpdb->prepare, $wpdb->query, or raw SQL statements.Affected if Plugin code contains unsanitized SQL queries without parameterized queries or prepared statements
-
Review WordPress error logs for SQL errorsAccess WordPress debug logs (wp-content/debug.log) or server error logs. Search for SQL syntax errors, warnings related to WPCRM database calls, or unusual SQL error messages.Affected if SQL errors or warnings involving WPCRM plugin queries appear in logs
-
Check for unauthorized database modificationsUse a database management tool (phpMyAdmin or command line) to inspect the WordPress database. Review user tables (wp_users, wp_usermeta) for unexpected administrative accounts or modified user privileges.Affected if Unexpected administrative accounts or altered user permissions are present in the database
A user is affected if the WPCRM plugin is installed with version 3.2.0 or below and contains unsanitized SQL queries susceptible to injection attacks.
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.
From vendor dataUpdate to the latest patched version of WPCRM when available. If no patch exists, review all database queries in the plugin and implement parameterized queries or prepared statements to neutralize SQL injection vectors.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24773 — 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-24773 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