dbcve.org
Wpshop 2WordPress extension · Eoxia

CVE-2015-10135

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-19
Fix available
A fix is available. Upgrade to 1.3.9.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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 WPshop 2 – E-Commerce plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the ajaxUpload function in versions before 1.3.9.6. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites 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 WPshop 2 WordPress plugin before version 1.3.9.6 lacks file type validation in its ajaxUpload function, allowing unauthenticated attackers to upload arbitrary files including malicious executables, potentially achieving remote code execution.

MitigationUpdate WPshop 2 plugin to version 1.3.9.6 or later; audit the server for unauthorized files uploaded before the patch and remove any malicious payloads.

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
Wpshop 2WordPress extension
Affected:< 1.3.9.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify if WPshop 2 plugin is installed
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named wpshop, wpshop-2, or similar Eoxia WPshop plugin folder
    Affected if The WPshop 2 plugin folder exists in the plugins directory
  2. Determine installed WPshop 2 version
    Open the main plugin PHP file (usually the primary PHP file in the plugin folder) and locate the version comment header or version constant. Compare the version number to 1.3.9.6
    Affected if The installed version is lower than 1.3.9.6
  3. Locate the ajaxUpload function
    Search within the WPshop plugin files for the function named ajaxUpload or ajax_upload
    Affected if The ajaxUpload function exists in the plugin code
  4. Verify the ajaxUpload endpoint is accessible
    Check if the WordPress AJAX endpoint (wp-admin/admin-ajax.php) exposes the wpshop ajaxUpload action to unauthenticated users by testing a request to the endpoint with the appropriate action parameter
    Affected if The ajaxUpload action is callable without authentication (no login required)
  5. Check for file type validation in ajaxUpload
    Review the ajaxUpload function code to see if there is any file type validation or extension checking before file save operations
    Affected if No file type validation is present, allowing any file extension to be uploaded

A user is affected if the WPshop 2 plugin version is below 1.3.9.6 AND the ajaxUpload function is present and accessible without authentication.

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 1.3.9.6 or later
Fixed in 1.3.9.6
Vendor patch plugins.trac.wordpress.org →
Interim mitigation

Update WPshop 2 plugin to version 1.3.9.6 or later; audit the server for unauthorized files uploaded before the patch and remove any malicious payloads.

Recommended fix High confidence

1.3.9.6

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate WPshop 2 plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.3.9.6 from wordpress.org/plugins/wpshop
  5. Verify the plugin version shows 1.3.9.6 after update
  6. Review uploads directory (/wp-content/uploads/) for any suspicious files that may have been uploaded during potential exploitation

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

Fix this in Wpshop 2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,100
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,360.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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