dbcve.org
Aliexpress Dropshipping With AlinextWordPress extension · Ali2woo

CVE-2024-2381

HIGH · 8.8 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 3.3.6 or later.
See remediation →
94/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
The AliExpress Dropshipping with AliNext Lite plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ajax_save_image function in all versions up to, and including, 3.3.5. This makes it possible for authenticated attackers, with subscriber-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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

The AliExpress Dropshipping with AliNext Lite WordPress plugin lacks file type validation in its ajax_save_image function, allowing authenticated users with subscriber-level access to upload arbitrary files to the server, which can lead to remote code execution.

MitigationUpdate the plugin to the latest version once available; if no update exists, disable the plugin or implement server-side file type validation and restrict upload functionality until a patch is released.

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
Aliexpress Dropshipping With AlinextWordPress extension
Affected:< 3.3.6

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
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 checks

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

  1. Confirm the plugin is installed
    Check your WordPress plugins directory for 'ali2woo' or 'aliexpress-dropshipping-with-alinext' folder, or list installed plugins via wp-cli: wp plugin list --name='*ali*'
    Affected if The plugin folder exists in wp-content/plugins/
  2. Identify the installed version
    Check the plugin header in main plugin file (usually ali2woo.php or alinext.php) for 'Version:' value, or run: wp plugin get ali2woo --field=version
    Affected if Version is present and less than 3.3.6
  3. Verify subscriber-level access exists
    Check WordPress user roles: go to Users > Roles in admin, or inspect wp_options table for wp_user_roles, or query: SELECT role FROM wp_usermeta WHERE meta_key='wp_capabilities' AND meta_value LIKE '%subscriber%'
    Affected if Any subscriber-level user accounts exist in the system
  4. Confirm the ajax_save_image endpoint is accessible
    Test access to /wp-admin/admin-ajax.php?action=ajax_save_image by submitting a request with a non-image file (e.g., a PHP file), or check plugin code for add_action('wp_ajax_ajax_save_image') registration
    Affected if The AJAX action responds or the hook is registered in the plugin code
  5. Check if file uploads are generally permitted
    Verify WordPress upload capability: check Media > Add New page accessibility for subscribers, or inspect wp_options for upload_filetypes setting, or verify the uploads directory is writable
    Affected if Subscriber role has upload capability or the uploads directory is writable

You are affected if the plugin is installed with version less than 3.3.6 AND any subscriber-level users exist AND the ajax_save_image AJAX endpoint is accessible without additional authorization checks.

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

Update the plugin to the latest version once available; if no update exists, disable the plugin or implement server-side file type validation and restrict upload functionality until a patch is released.

Recommended fix High confidence

Aliexpress Dropshipping with AliNext Lite version 3.3.6

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Aliexpress Dropshipping with AliNext Lite' plugin
  4. Click 'Update Now' if an update is available, or manually update to version 3.3.6
  5. Verify the plugin is updated to version 3.3.6 or later
  6. Check the site's file system for any suspicious files that may have been uploaded during any potential exploitation

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

Fix this in Aliexpress Dropshipping With Alinext Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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