AutomatewooWordPress extension · Woocommerce
CVE-2023-33318
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 · uneditedUnrestricted Upload of File with Dangerous Type vulnerability in WooCommerce AutomateWoo.This issue affects AutomateWoo: from n/a through 4.9.40.
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 confidenceUnrestricted file upload vulnerability in AutomateWoo plugin for WooCommerce allows attackers to upload dangerous file types (potentially malicious scripts) without proper validation, which could lead to remote code execution on the WordPress site.
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
<= 4.9.40CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify AutomateWoo plugin is installedCheck WordPress plugins directory or access WP Admin > Plugins to confirm AutomateWoo is present and activeAffected if AutomateWoo plugin is installed and active on the WordPress site
-
Check installed AutomateWoo versionNavigate to WP Admin > Plugins > Installed Plugins > AutomateWoo, or inspect the plugin header in /wp-content/plugins/automatewoo/includes/automatewoo.php to find the Version fieldAffected if Version number is 4.9.40 or lower
-
Identify if Workflows with file upload actions existGo to AutomateWoo > Workflows in WP Admin, review any workflows that may include upload actions or are triggered by frontend submission forms that accept file attachmentsAffected if Active workflows contain file upload actions or accept file submissions from users
-
Review file upload configuration settingsCheck AutomateWoo settings at AutomateWoo > Settings, or inspect the database options table for automatewoo options related to file uploads and allowed file typesAffected if File upload functionality is enabled with no restrictions or weak validation on allowed file types
The environment is affected if AutomateWoo version 4.9.40 or lower is installed AND file upload features are enabled or accessible to users, allowing potentially malicious file types to be uploaded.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate AutomateWoo to the latest version beyond 4.9.40 to patch the unrestricted upload vulnerability. Review and restrict file upload functionality to allow only safe file types.
Fix this in Automatewoo
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-33318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-33318 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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