Security readout for executives and security teams
Plain-English summary
CVE-2015-9339 affects the WordPress wp-file-upload plugin before version 2.7.1. The plugin did not sufficiently restrict JavaScript file uploads. That could let an attacker place script files where the site may later serve them. The source data does not provide CVSS, affected configuration details, or confirmed exploitation.
Executive priority
Prioritize validation on public WordPress sites using this plugin. Urgency increases if anonymous uploads are enabled, but source evidence is too limited for a confirmed high-severity rating.
Technical view
The CVE describes insufficient upload restrictions for .js files in wp-file-upload before 2.7.1. The bundle does not identify CWE, CVSS, authentication requirements, upload destination behavior, or whether uploaded JavaScript is executable in a victim browser context.
Likely exposure
Exposure is limited to WordPress sites running the wp-file-upload plugin earlier than 2.7.1, especially where upload forms are reachable by untrusted users.
Exploitation context
The bundle does not show CISA KEV listing, active exploitation, public exploit details, or exploitation prerequisites. Treat exploitability as unconfirmed from these sources.
Researcher notes
Key missing evidence includes CVSS, CWE, authorization model, upload storage path, browser execution conditions, and fixed-version changelog details. Avoid assuming remote code execution or active exploitation from this bundle alone.
Mitigation direction
- Upgrade wp-file-upload to version 2.7.1 or later.
- Check the WordPress plugin developer page for current vendor guidance.
- Restrict upload access to trusted users until remediation is confirmed.
- Review uploaded files and remove unexpected .js files.
Validation and detection
- Inventory WordPress sites for the wp-file-upload plugin.
- Confirm installed plugin versions are 2.7.1 or later.
- Identify upload forms exposed to anonymous or low-trust users.
- Review upload directories for JavaScript files created before remediation.
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.
CVE-2015-9339 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://wordpress.org/plugins/wp-file-upload/#developersCVE reference · x_refsource_MISC
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.