dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-22710

HIGH · 7.6 CVSS v3.1 Published 2025-01-21
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 storeapps Smart Manager smart-manager-for-wp-e-commerce allows Blind SQL Injection.This issue affects Smart Manager: from n/a through <= 8.52.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 confidence

A blind SQL injection vulnerability exists in the Smart Manager plugin for WordPress e-commerce sites. The vulnerability allows unauthenticated attackers to inject malicious SQL queries through unsanitized input parameters. Blind SQL injection means attackers infer information from application responses (e.g., time-based delays or true/false conditions) rather than seeing direct database output.

MitigationUpgrade Smart Manager to a version beyond 8.52.0 that contains the patched code. If immediate patching is not possible, consider disabling the plugin or implementing a WAF rule to filter malicious SQL payloads targeting the affected parameters.

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. Locate the installed Smart Manager plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find Smart Manager. The version number is displayed under the plugin name. Alternatively, access the plugin's main PHP file (typically smart-manager.php or similar) in wp-content/plugins/smart-manager/ and look for the 'Version' header in the file comments.
    Affected if The version is 8.52.0 or lower, as these versions contain the vulnerable code
  2. Confirm the site uses WordPress e-commerce functionality
    Verify the WordPress site runs an e-commerce setup (such as WooCommerce) and has Smart Manager activated for managing store data. This vulnerability targets e-commerce sites specifically.
    Affected if Smart Manager is active on an e-commerce WordPress site running a vulnerable version
  3. Identify exposed input parameters
    Review HTTP requests to the site that interact with Smart Manager (typically through /wp-admin/admin-ajax.php or similar endpoints). The vulnerability exists in unsanitized input parameters that the plugin processes. Check for parameters related to search, filtering, or data export functions.
    Affected if The site processes unauthenticated requests to Smart Manager endpoints with user-supplied input parameters without sanitization

A site is affected if it runs Smart Manager version 8.52.0 or lower, is used for e-commerce, and processes user input through the plugin's vulnerable parameters.

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 Smart Manager to a version beyond 8.52.0 that contains the patched code. If immediate patching is not possible, consider disabling the plugin or implementing a WAF rule to filter malicious SQL payloads targeting the affected parameters.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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