dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-30633

CRITICAL · 9.3 CVSS v3.1 Published 2026-01-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 AA-Team Amazon Native Shopping Recommendations allows SQL Injection.This issue affects Amazon Native Shopping Recommendations: from n/a through 1.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 confidence

SQL Injection vulnerability in AA-Team Amazon Native Shopping Recommendations plugin allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability affects versions 1.3 and earlier, enabling remote attackers to potentially execute arbitrary SQL queries against the database.

MitigationImplement prepared statements/parameterized queries for all database operations and apply proper input validation and escaping for all user-supplied data before using it in SQL queries.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Amazon Native Shopping Recommendations plugin is installed
    Check the WordPress plugin directory for 'amazon-native-shopping-recommendations' folder, or list all installed plugins via wp-cli: wp plugin list --status=active --format=csv or check via WordPress admin plugins page
    Affected if The AA-Team Amazon Native Shopping Recommendations plugin is present and active in the WordPress installation
  2. Check installed plugin version
    Read the plugin header file (usually main PHP file or readme.txt) to find the Version field, or query via wp-cli: wp plugin get amazon-native-shopping-recommendations --field=version
    Affected if Version is 1.3 or earlier (1.0, 1.1, 1.2, 1.3, or any version below the fixed release)
  3. Identify if plugin handles user-supplied search or input parameters
    Review plugin source code for $_GET, $_POST, or $_REQUEST usage in SQL query contexts; check if search/browse features accept user input that could reach database queries
    Affected if The plugin processes user input (such as search terms, category filters, or URL parameters) directly into SQL queries without prepared statements
  4. Check for signs of SQL injection exploitation
    Review web server access logs for suspicious SQL patterns in requests to plugin endpoints (look for UNION SELECT, OR 1=1, common SQL injection payloads); check database for unexpected tables, modified admin accounts, or unauthorized data access
    Affected if Logs show SQL injection attempts targeting the plugin or database shows evidence of unauthorized SQL execution
  5. Verify input sanitization is absent in vulnerable code paths
    Examine plugin PHP files for direct variable interpolation in SQL strings (e.g., "SELECT * FROM ... WHERE term = '$term'") versus parameterized queries (PDO prepare, $wpdb->prepare)
    Affected if SQL queries concatenate user input directly without using $wpdb->prepare(), prepared statements, or input sanitization functions

The environment is affected if the AA-Team Amazon Native Shopping Recommendations plugin is installed with version 1.3 or earlier and the plugin processes user input into database queries without proper 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.

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

Implement prepared statements/parameterized queries for all database operations and apply proper input validation and escaping for all user-supplied data before using it in SQL queries.

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-30633 — 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-30633 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