CVE-2016-15043: Wp Mobile Detector Project Wp Mobile Detector remote code execution (CVSS 9.8)

Description

The WP Mobile Detector plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in resize.php file in versions up to, and including, 3.5. 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

Wp Mobile Detector Project Wp Mobile Detector≤ 3.5

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://aadityapurani.com/2016/06/03/mobile-detector-poc/ExploitThird Party Advisory
https://blog.sucuri.net/2016/06/wp-mobile-detector-vulnerability-being-exploited-in-the-wild.htmlExploitPress/Media Coverage
https://wordpress.org/plugins/wp-mobile-detector/changelog/Product
https://wpscan.com/vulnerability/e4739674-eed4-417e-8c4d-2f5351b057cfExploitThird Party Advisory
https://www.pluginvulnerabilities.com/2016/05/31/aribitrary-file-upload-vulnerability-in-wp-mobile-detector/ExploitThird Party Advisory
https://www.wordfence.com/threat-intel/vulnerabilities/id/5a5d5dbd-36f0-4886-adf8-045ec9c2e306?source=cveThird Party Advisory

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2016-15043 being actively exploited?

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

How severe is CVE-2016-15043?

CVE-2016-15043 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 8.52% probability of exploitation.

Which products are affected by CVE-2016-15043?

Affected products include Wp Mobile Detector Project Wp Mobile Detector.

How do I fix CVE-2016-15043?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2016-15043 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