dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-31619

HIGH · 8.5 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/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 marcoingraiti Actionwear products sync actionwear-products-sync allows SQL Injection.This issue affects Actionwear products sync: from n/a through <= 2.3.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 the marcoingraiti Actionwear products sync WordPress plugin (versions <= 2.3.3) allows attackers to inject malicious SQL commands through unsanitized user input, potentially enabling unauthorized data extraction, modification, or deletion from the underlying database.

MitigationUpdate to the latest patched version of the Actionwear products sync plugin immediately. As an interim measure, restrict plugin access and review server-side logs for suspicious SQL-like patterns.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Actionwear products sync plugin
    Check the WordPress plugins directory (wp-content/plugins/) for a folder containing 'actionwear' or 'marcoingraiti'. Also check wp-content/plugins/actionwear-products-sync/ or similar naming.
    Affected if The plugin folder exists in the WordPress plugins directory
  2. Identify the installed version
    Open the main plugin PHP file (usually named the same as the plugin folder) and look in the plugin header comment for 'Version: X.X.X'. Alternatively, check the readme.txt file in the plugin folder.
    Affected if The version number is 2.3.3 or lower (any version <= 2.3.3)
  3. Confirm the plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify the Actionwear products sync plugin shows as 'Active', or query the wp_options table for option_name = 'active_plugins' and check if the plugin is listed.
    Affected if The plugin appears in the active plugins list
  4. Identify the vulnerable code entry point
    Search the plugin PHP files for SQL-related functions (wpdb->prepare, $wpdb->query, etc.) that process user input from $_GET, $_POST, or $_REQUEST without proper sanitization. Focus on files handling product sync functionality.
    Affected if Code exists that passes user input directly into SQL queries without using $wpdb->prepare() or equivalent sanitization
  5. Review access to the vulnerable endpoint
    Determine if the vulnerable code is accessible via WordPress AJAX (admin-ajax.php) or front-end requests. Check for add_action('wp_ajax_...') or add_action('wp_ajax_nopriv_...') hooks tied to the sync functionality.
    Affected if The vulnerable functionality is hooked to an AJAX endpoint accessible to unauthenticated users (wp_ajax_nopriv_) or to users with low privileges
  6. Check for signs of exploitation in logs
    Review web server access logs and WordPress debug logs for suspicious SQL-like patterns (UNION SELECT, OR 1=1, DROP TABLE, etc.) in requests targeting the plugin's sync endpoints.
    Affected if Log entries show SQL injection attempts or unexpected SQL errors originating from the plugin's URLs

A user is affected if the Actionwear products sync plugin is installed, active, and running version 2.3.3 or lower, with the vulnerable SQL code accessible through an exposed endpoint.

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

Update to the latest patched version of the Actionwear products sync plugin immediately. As an interim measure, restrict plugin access and review server-side logs for suspicious SQL-like patterns.

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