Security readout for executives and security teams
Plain-English summary
This issue affects WordPress sites running Showbiz Pro through version 1.7.1. The reported flaw allows PHP code execution by uploading a PHP file inside a ZIP archive. That can turn a plugin upload path into server-side code execution. The public record does not provide CVSS scoring, confirmed active exploitation, or a vendor fix.
Executive priority
Prioritize internet-facing WordPress sites first, especially if Showbiz Pro is installed. Treat confirmed vulnerable instances as urgent because the reported impact is server-side PHP code execution.
Technical view
CVE-2015-9499 describes PHP code execution in the Showbiz Pro WordPress plugin through 1.7.1 via a PHP file contained in an uploaded ZIP archive. Public exploit references exist, including Exploit-DB and a GitHub module. The source bundle does not identify a CWE, CVSS vector, patch version, or KEV-listed exploitation.
Likely exposure
Exposure is likely limited to WordPress installations with Showbiz Pro installed at version 1.7.1 or earlier. Sites without this plugin are not indicated as affected by the provided sources.
Exploitation context
The issue has public exploit references, which raises practical risk. However, the bundle marks KEV as false and provides no cited evidence of active exploitation in the wild.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, or patch information is included. Analysis relies on the CVE description and public exploit references. Do not claim active exploitation without additional evidence.
Mitigation direction
- Inventory WordPress sites for Showbiz Pro and record installed versions.
- Disable or remove Showbiz Pro where it is not required.
- Check vendor or trusted vulnerability guidance for an official fixed version.
- Review upload and plugin directories for unexpected PHP files.
- Restrict administrative access and file upload permissions where possible.
Validation and detection
- Confirm whether Showbiz Pro is installed on each WordPress site.
- Verify any installed version is not 1.7.1 or earlier.
- Review web logs for suspicious ZIP uploads or unexpected PHP requests.
- Inspect plugin and upload paths for unauthorized PHP files.
- Confirm remediation matches vendor or trusted vulnerability guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Execution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2015-9499 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://wpvulndb.com/vulnerabilities/7955CVE reference · x_refsource_MISC
- https://github.com/espreto/wpsploit/blob/master/modules/exploits/unix/webapp/wp_showbiz_file_upload.rbCVE reference · x_refsource_MISC
- 35385CVE reference · exploit, x_refsource_EXPLOIT-DB
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.