Skip to content
Fencer Intel
medium 6.8

CVE-2013-7102 json

Multiple unrestricted file upload vulnerabilities in (1) media-upload.php, (2) media-upload-lncthumb.php, and (3) media-upload-sq_button.ph…

published 12y ago modified 4mo ago also EUVD-2013-6888

cvss
6.8
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
14.8%
EPSS 14.8% chance of exploitation in 30 days, percentile 96%
public exploits
1
Metasploit

Summary

Multiple unrestricted file upload vulnerabilities in (1) media-upload.php, (2) media-upload-lncthumb.php, and (3) media-upload-sq_button.php in lib/admin/ in the OptimizePress theme before 1.61 for WordPress allow remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in images_comingsoon, images_lncthumbs, or images_optbuttons in wp-content/uploads/optpress/, as exploited in the wild in November 2013.

Is CVE-2013-7102 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/unix/webapp/wp_optimizepress_upload)
  2. Published

Exploit prediction

14.80% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/unix/webapp/wp_optimizepress_upload WordPress OptimizePress Theme File Upload Vulnerability metasploit exploit, excellent rank, 2013-11-29
  • osirt.com http://www.osirt.com/2013/11/wordpress-optimizepress-hack-file-upload-vulnerability/ referenced PoC, tagged "exploit" by a source, unverified
  • blog.sucuri.net http://blog.sucuri.net/2013/12/wordpress-optimizepress-theme-file-upload-vulnerability.html referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 6.8 AV:N/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-20 Improper Input Validation
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.