dbcve.org
Seo Plugin By Squirrly SeoWordPress extension · Squirrly

CVE-2025-22783

HIGH · 8.8 CVSS v3.1 Published 2025-03-27
Fix available
A fix is available. Upgrade to after 12.4.03 or later.
See remediation →
94/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 SEO Squirrly SEO Plugin by Squirrly SEO squirrly-seo allows SQL Injection.This issue affects SEO Plugin by Squirrly SEO: from n/a through <= 12.4.03.

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 SEO Squirrly SEO Plugin allows attackers to inject malicious SQL commands through unsanitized user input that gets directly incorporated into database queries. The vulnerability exists in versions up to and including 12.4.03 of the plugin.

MitigationUpdate the SEO Plugin by Squirrly SEO to the latest version once available. If no patch exists, disable the plugin until a fix is released. Alternatively, identify and sanitize the vulnerable code paths using prepared statements for all database queries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Seo Plugin By Squirrly SeoWordPress extension
Affected:<= 12.4.03

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate the Squirrly SEO plugin and identify its version
    Navigate to WordPress admin > Plugins > Installed Plugins and find 'SEO Plugin by Squirrly SEO'. Read the version number from the plugin description, or inspect the main plugin file (typically squirrly-seo/squirrly.php) and look for the 'Version:' header comment.
    Affected if The installed version is 12.4.03 or lower.
  2. Verify the exact version number in the plugin header
    Access the plugin directory via FTP or file manager at wp-content/plugins/squirrly-seo/ and open the main PHP file. Locate the 'Version:' constant or variable that defines the plugin version.
    Affected if The version string reads '12.4.03' or any version number lower than 12.4.03.
  3. Identify PHP files handling database queries within the plugin
    Search the plugin directory for files containing '$wpdb->prepare', '$wpdb->query', or direct SQL concatenation. Common locations include classes or models that handle SEO audits, keyword tracking, or settings storage.
    Affected if The plugin contains SQL query code that does not use prepared statements, or where user input is concatenated directly into query strings.
  4. Review database query handling for unsanitized input
    Examine PHP files that process user-supplied data (GET/POST parameters, request variables) and pass them into SQL queries without sanitization functions like $wpdb->prepare() or esc_sql().
    Affected if User input from request parameters is directly concatenated into SQL queries without escaping or prepared statement usage.
  5. Inspect database and web server logs for suspicious SQL patterns
    Check MySQL general query log (if enabled) or web server access logs for unusual SQL syntax, UNION-based queries, or common SQL injection payloads targeting the Squirrly plugin endpoints.
    Affected if Logs contain SQL injection attempt patterns or unexpected SQL commands originating from requests to Squirrly plugin functionality.

You are affected if the Squirrly SEO plugin version is 12.4.03 or lower and the plugin processes user input in database queries without proper sanitization or prepared statements.

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
Upgrade available Upgrade to a release after 12.4.03
Interim mitigation

Update the SEO Plugin by Squirrly SEO to the latest version once available. If no patch exists, disable the plugin until a fix is released. Alternatively, identify and sanitize the vulnerable code paths using prepared statements for all database queries.

Recommended fix Moderate confidence

Squirrly SEO plugin version > 12.4.03 (latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'SEO Plugin by Squirrly SEO' plugin
  4. 4. Check the current installed version (should be <= 12.4.03)
  5. 5. Navigate to Plugins > Add New > Upload Plugin (or check for updates via Dashboard > Updates)
  6. 6. Update to the latest available version of the Squirrly SEO plugin
  7. 7. Verify the update was successful by confirming the new version number

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

Fix this in Seo Plugin By Squirrly Seo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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