dbcve.org
Aliexpress Dropshipping With AlinextWordPress extension · Ali2woo

CVE-2024-4450

MEDIUM · 6.3 CVSS v3.1 Published 2024-06-19
Fix available
A fix is available. Upgrade to 3.3.7 or later.
See remediation →
69/100
Remediation priority · Elevated
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 unauthorized access due to a missing capability check on several functions in the ImportAjaxController.php file in all versions up to, and including, 3.3.6. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform several actions like importing and modifying products. CVE-2024-37210 is likely a duplicate of this issue.

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 AliNext Lite WordPress plugin lacks capability checks on AJAX functions in ImportAjaxController.php, allowing any authenticated user with subscriber-level permissions to import and modify products that should require administrator privileges.

MitigationUpdate the plugin to version 3.3.7 or later which includes proper capability validation on the affected ImportAjaxController functions. If immediate update is not possible, manually add current_user_can() checks to all sensitive AJAX endpoints.

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

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Verify the Ali2woo Aliexpress Dropshipping plugin is installed
    Navigate to WordPress Admin > Plugins and look for 'Ali2woo Aliexpress Dropshipping With Alinext' or check the /wp-content/plugins/ directory for a folder named ali2woo_aliexpress_dropshipping or similar
    Affected if The plugin is present in the WordPress installation
  2. Identify the installed plugin version
    In WordPress Admin > Plugins, click on the plugin to view details and locate the version number, or inspect the main plugin file header for the Version field
    Affected if The version is lower than 3.3.7 (e.g., 3.3.6, 3.3.5, etc.)
  3. Confirm non-administrator user accounts exist
    Go to WordPress Admin > Users and review the user list to see if any users have roles below Administrator (such as Subscriber, Contributor, Author, or Editor)
    Affected if There is at least one user with Subscriber-level or higher access who is not an Administrator
  4. Verify the vulnerable AJAX endpoint is accessible
    The vulnerability exists in the ImportAjaxController.php file within the plugin. Check if this file exists in the plugin directory and if the site allows AJAX requests from authenticated non-admin users to endpoints controlled by this controller
    Affected if The plugin is installed with version below 3.3.7 and the AJAX endpoints do not enforce capability checks (this would require code review or penetration testing to confirm)

You are affected if the Ali2woo Aliexpress Dropshipping With Alinext plugin is installed at a version below 3.3.7 on your WordPress site and you have any authenticated users with roles below Administrator.

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

Update the plugin to version 3.3.7 or later which includes proper capability validation on the affected ImportAjaxController functions. If immediate update is not possible, manually add current_user_can() checks to all sensitive AJAX endpoints.

Recommended fix High confidence

3.3.7

  1. Backup your WordPress site before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Find 'AliExpress Dropshipping with AliNext Lite' plugin
  4. Click 'Update now' if an update is available, or manually upload version 3.3.7 of the plugin
  5. Verify the plugin updated successfully to version 3.3.7 or higher
  6. Test that the plugin functionality works as expected after the update

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