dbcve.org
Dropshipping \& Affiliation With AmazonWordPress extension · Amadercode

CVE-2023-31215

HIGH · 8.8 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to after 2.1.2 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
Unrestricted Upload of File with Dangerous Type vulnerability in AmaderCode Lab Dropshipping & Affiliation with Amazon.This issue affects Dropshipping & Affiliation with Amazon: from n/a through 2.1.2.

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

This is an unrestricted file upload vulnerability in the AmaderCode Lab Dropshipping & Affiliation with Amazon plugin (versions through 2.1.2). The plugin fails to properly validate file types during upload, allowing attackers to upload dangerous file types (such as executable scripts) that could lead to remote code execution.

MitigationImplement strict allowlist-based file type validation on upload, verify file content (magic bytes) rather than just extension, store uploads outside webroot or disable script execution in the upload directory, and require authentication for upload functionality.

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
Dropshipping \& Affiliation With AmazonWordPress extension
Affected:<= 2.1.2

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. Verify plugin installation
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Amadercode Dropshipping & Affiliation With Amazon' in the list of active or inactive plugins.
    Affected if The plugin appears in the plugin list regardless of activation status.
  2. Confirm installed version
    Click on the plugin name/details to view the version number displayed in the plugin header, or inspect the plugin's main PHP file for a 'Version' comment or defined constant.
    Affected if The displayed version number is 2.1.2 or lower.
  3. Identify upload functionality
    Search the plugin directory (wp-content/plugins/) for files handling file uploads, such as those containing 'upload', 'file', or 'POST' method handling in PHP. Look for form endpoints or AJAX actions related to file uploads.
    Affected if The plugin contains upload handling code and the upload endpoint is accessible without stricter authentication than standard WordPress admin access.
  4. Inspect upload directory
    Check common WordPress upload paths (wp-content/uploads/, wp-content/uploads/[year]/, or custom paths defined in Media Settings) for unexpected PHP files, scripts, or files with double extensions (e.g., image.php.jpg).
    Affected if Unexpected executable or script files are found in upload directories, especially those containing the plugin's name or suspicious patterns.
  5. Check for web shells
    Use file integrity monitoring or grep commands to search upload directories for PHP files containing common web shell patterns (eval, base64_decode, system, shell_exec, or suspicious encoded content).
    Affected if PHP files with code execution functions or obfuscated content are found in upload directories.

You are likely affected if the Amadercode Dropshipping & Affiliation With Amazon plugin (version 2.1.2 or lower) is installed and its upload functionality is accessible, or if suspicious executable files exist in upload directories.

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
Upgrade available Upgrade to a release after 2.1.2
Interim mitigation

Implement strict allowlist-based file type validation on upload, verify file content (magic bytes) rather than just extension, store uploads outside webroot or disable script execution in the upload directory, and require authentication for upload functionality.

Fix this in Dropshipping \& Affiliation With Amazon Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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