CVE-2015-10135

Eoxia Wpshop 2 remote code execution

9.8 CRITICALPublic exploitEPSS 3.98%

Published19 Jul 2025

Description

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Eoxia Wpshop 2< 1.3.9.6

Remediation

Fixed in

Eoxia Wpshop 2≥ 1.3.9.6

Patch & vendor advisories

https://plugins.trac.wordpress.org/changeset/1103406

References

https://g0blin.co.uk/g0blin-00036/ExploitThird Party Advisory
https://github.com/espreto/wpsploit/blob/master/modules/exploits/unix/webapp/wp_wpshop_ecommerce_file_upload.rbProduct
https://plugins.trac.wordpress.org/changeset/1103406Patch
https://wordpress.org/plugins/wpshop/#developersProduct
https://www.wordfence.com/threat-intel/vulnerabilities/id/32e8224d-a653-48d7-a3f4-338fc0c1dc77?source=cveThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2015-10135 being actively exploited?

CVE-2015-10135 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 3.98%.

How severe is CVE-2015-10135?

CVE-2015-10135 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 3.98% probability of exploitation.

Which products are affected by CVE-2015-10135?

Affected products include Eoxia Wpshop 2.

How do I fix CVE-2015-10135?

Upgrade affected software to a fixed version, for example Eoxia Wpshop 2 1.3.9.6 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2015-10135 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.