dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-68060

HIGH · 7.6 CVSS v3.1 Published 2026-05-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 WPMart Team Member allows Blind SQL Injection. This issue affects Team Member: from n/a through 8.5.

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

A blind SQL injection vulnerability exists in the WPMart Team Member WordPress plugin (versions through 8.5). The vulnerability allows authenticated attackers to inject arbitrary SQL commands through unsanitized user input, potentially enabling data exfiltration or database manipulation. As a blind SQL injection, attackers infer results through behavioral differences rather than direct output.

MitigationUpgrade the Team Member plugin to a version beyond 8.5 that includes proper input sanitization using prepared statements or parameterized queries for all database interactions. If no patched version exists, implement immediate input validation and escaping at the application layer as a temporary measure.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Confirm WPMart Team Member plugin installation
    Navigate to WordPress admin dashboard > Plugins and locate the Team Member plugin by WPMart. Note its current version number displayed in the plugin details.
    Affected if The plugin is installed and active on the WordPress site.
  2. Compare installed version to affected range
    Check if the installed version is 8.5 or lower. The vulnerability affects all versions through 8.5. If your version is 8.5 or below, you are within the affected range.
    Affected if The installed version is 8.5 or lower.
  3. Identify authentication requirements
    Review the plugin settings and determine which WordPress user roles have access to the Team Member plugin features. Check if lower-privileged users (such as subscribers or contributors) can access plugin functionality.
    Affected if The plugin allows access to authenticated users with limited privileges (subscriber, contributor, or author roles) who can submit input through the plugin.
  4. Inspect plugin database interaction points
    If you have file access, examine the plugin PHP files for direct SQL queries that incorporate user-supplied parameters without using $wpdb->prepare() or parameterized queries. Look for functions handling member data input (name, bio, role, social links).
    Affected if Plugin code contains SQL queries built with string concatenation or unsanitized input from $_POST, $_GET, or $_REQUEST variables.
  5. Monitor for anomalous database behavior
    Enable WordPress debug logging (wp-config.php: define( 'WP_DEBUG', true );) and review database query logs. Watch for unusual query patterns or delays that could indicate blind SQL injection testing.
    Affected if Unexpected or repetitive database queries appear in logs, particularly involving the plugin's database tables, without corresponding legitimate admin actions.

You are affected if the WPMart Team Member plugin is installed at version 8.5 or below and allows authenticated users to access plugin features that accept user input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Team Member plugin to a version beyond 8.5 that includes proper input sanitization using prepared statements or parameterized queries for all database interactions. If no patched version exists, implement immediate input validation and escaping at the application layer as a temporary measure.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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