dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-26590

HIGH · 7.6 CVSS v3.1 Published 2025-06-06
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 Nir Complete Google Seo Scan complete-google-seo-scan allows SQL Injection.This issue affects Complete Google Seo Scan: from n/a through <= 3.5.1.

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 Complete Google Seo Scan WordPress plugin allows remote attackers to inject malicious SQL commands via unsanitized input parameters, potentially leading to unauthorized database access, data exfiltration, or manipulation.

MitigationUpdate to the latest patched version of Complete Google Seo Scan; if no patch available, implement parameterized queries/prepared statements for all database interactions and apply input validation as a temporary compensating control.

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 plugin installation
    Access WordPress admin dashboard and navigate to Plugins > Installed Plugins, or check the wp-content/plugins directory for a folder named 'complete-google-seo-scan' or similar
    Affected if The Complete Google Seo Scan plugin appears in the installed plugins list
  2. Determine installed version
    In the WordPress plugins list, locate the Complete Google Seo Scan plugin and note the version number displayed under the plugin name. Alternatively, open the main plugin PHP file and read the Version field from the plugin header comment
    Affected if The version cannot be determined or is older than the patched version released for this CVE
  3. Identify plugin database interaction points
    Examine the plugin's PHP source files for direct SQL query construction using functions like $wpdb->query, $wpdb->get_results, or mysql_query where user-supplied input from $_GET, $_POST, $_REQUEST, or similar superglobals is used without sanitization functions such as $wpdb->prepare, esc_sql, or intval
    Affected if Database queries receive raw user input without parameterized queries or input sanitization
  4. Test accessible parameter endpoints
    Identify plugin pages or AJAX endpoints that accept user input. Use the browser developer tools or a web proxy to inspect form inputs, query string parameters, and POST data sent to the plugin. Manually submit characters like single quotes (') to input fields and observe if SQL errors appear in the response
    Affected if SQL syntax errors or unexpected database behavior occurs in response to specially crafted input
  5. Review web server access logs
    Search Apache, Nginx, or other web server logs for requests to the plugin's PHP files that contain SQL operators (AND, OR, UNION, SELECT) or special characters in parameter values, indicating potential exploitation attempts
    Affected if Log entries show SQL injection patterns targeting the plugin's input parameters

The environment is affected if the Complete Google Seo Scan plugin is installed and processes user-supplied input in SQL queries without using prepared statements or proper input sanitization.

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

Update to the latest patched version of Complete Google Seo Scan; if no patch available, implement parameterized queries/prepared statements for all database interactions and apply input validation as a temporary compensating control.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (version > 3.5.1)

  1. Update the Complete Google Seo Scan plugin to the latest available version from the WordPress plugin repository
  2. If an update is not immediately available, consider temporarily disabling the plugin until a patched version is released
  3. After updating, verify the plugin functionality and monitor for any unusual behavior
  4. Check the plugin's changelog or the vendor's website for security-related update notes

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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