dbcve.org
AutomatewooWordPress extension · Woocommerce

CVE-2023-33330

HIGH · 8.1 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to 4.9.51 or later.
See remediation →
87/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 WooCommerce AutomateWoo.This issue affects AutomateWoo: from n/a through 4.9.50.

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 WooCommerce AutomateWoo plugin allows attackers to inject malicious SQL commands through unsanitized user input. The vulnerability affects versions through 4.9.50 and could enable unauthorized data access or manipulation of database records.

MitigationUpdate AutomateWoo to the latest patched version once available. Until then, restrict administrative access to trusted users and implement WAF rules to detect SQL injection patterns.

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
AutomatewooWordPress extension
Affected:< 4.9.51

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
None

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

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 AutomateWoo plugin is installed
    Navigate to WordPress admin > Plugins and verify AutomateWoo appears in the installed plugins list, or inspect the file /wp-content/plugins/automatewoo/automatewoo.php
    Affected if Plugin is not installed
  2. Check installed AutomateWoo version
    In WordPress admin, go to Plugins > Installed Plugins > AutomateWoo and read the version number displayed, or check the version constant in /wp-content/plugins/automatewoo/automatewoo.php
    Affected if Version is lower than 4.9.51
  3. Verify WordPress user roles with access
    Navigate to Users > All Users in WordPress admin and review which users have Administrator or Shop Manager roles, as the vulnerability can be exploited through these privileged accounts
    Affected if Any untrusted or compromised user account has Administrator or Shop Manager privileges
  4. Inspect server access logs for SQL injection patterns
    Search web server access logs (typically in /var/log/nginx/ or /var/log/apache2/) for requests to /wp-admin/admin-ajax.php containing SQL keywords like UNION, SELECT, INSERT, or common SQL injection payloads in AutomateWoo-related action parameters
    Affected if Suspicious SQL injection patterns found in logs targeting AutomateWoo endpoints
  5. Check for unauthorized database modifications
    Review WordPress database tables, particularly wp_options and any custom AutomateWoo tables, for unexpected or unauthorized entries that may indicate successful SQL injection exploitation
    Affected if Unexpected data or modifications found in database

You are affected if AutomateWoo version is below 4.9.51 and the plugin is active with untrusted users having administrative access

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 4.9.51 or later
Fixed in 4.9.51
Interim mitigation

Update AutomateWoo to the latest patched version once available. Until then, restrict administrative access to trusted users and implement WAF rules to detect SQL injection patterns.

Recommended fix Moderate confidence

AutomateWoo version 4.9.51

  1. 1. Create a complete backup of your WordPress site, including database and files
  2. 2. Update AutomateWoo plugin to version 4.9.51 or later through WordPress admin > Plugins > Plugins List > click Update Now for AutomateWoo
  3. 3. Alternatively, update via WP-CLI: wp plugin update automatewoo
  4. 4. After update, clear any caching systems and verify the site functions normally
  5. 5. Test critical AutomateWoo workflows to ensure functionality is intact

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

Fix this in Automatewoo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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