CVE-2025-31551
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 Salesmate.io Salesmate Add-On for Gravity Forms gf-salesmate-add-on allows SQL Injection.This issue affects Salesmate Add-On for Gravity Forms: from n/a through <= 2.0.3.
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 confidenceSQL injection vulnerability in Salesmate Add-On for Gravity Forms (gf-salesmate-add-on) allows attackers to inject malicious SQL commands through unsanitized input. The flaw stems from improper neutralization of special elements in SQL queries, enabling database manipulation. This critical flaw (CVSS 9.3) affects all versions up to and including 2.0.3.
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.
-
Confirm Salesmate Add-On for Gravity Forms is installedNavigate to WordPress admin > Plugins and look for 'Salesmate Add-On for Gravity Forms' in the installed plugins listAffected if The plugin appears in the installed plugins list and is activated
-
Identify the plugin versionClick on the plugin in the WordPress plugins list to view its details, or inspect the plugin header in wp-content/plugins/salesmate-gravity-forms-addon/ folder for the 'Version' fieldAffected if Version cannot be determined or falls within the affected range announced by the vendor
-
Check for suspicious database queries in logsReview WordPress debug logs (wp-content/debug.log if logging is enabled) and server access logs for unusual or malformed SQL queries originating from the plugin endpointsAffected if Unexpected SQL syntax or union-based queries appear in logs related to the plugin
-
Inspect for unauthorized database changesQuery the WordPress database for unexpected changes: check wp_options for suspicious entries, review user tables for unauthorized accounts, and examine form entries for unexpected dataAffected if Unexpected database modifications, new admin users, or suspicious form data entries are found
A user is affected if the Salesmate Add-On for Gravity Forms plugin is installed and active, and their installed version matches the affected range or cannot be verified against vendor advisories.
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 a patched version of the Salesmate Add-On for Gravity Forms when released. If no patch is available, disable the plugin or restrict administrative access until remediation is possible. Implement parameterized queries or prepared statements for all database interactions.
- Consultation3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-31551 — 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-31551 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