Security readout for executives and security teams
Plain-English summary
This CVE concerns the WordPress wp-file-upload plugin before version 3.4.1. The plugin did not sufficiently restrict uploads of files ending in .php.js. That is concerning because upload validation failures can expose public websites to malicious file placement, depending on server handling and configuration.
Executive priority
Prioritize discovery and upgrade for internet-facing WordPress sites. The available evidence is too limited for a precise severity rating, but upload validation weaknesses on public websites can create material exposure if left unverified.
Technical view
The record describes an upload restriction weakness in wp-file-upload before 3.4.1 involving .php.js filenames. The public bundle does not provide CVSS, CWE, CPEs, exploit mechanics, or confirmed impact. Treat exposure as plugin-version dependent and validate against WordPress plugin release information.
Likely exposure
WordPress sites running wp-file-upload versions earlier than 3.4.1, especially sites exposing upload forms to unauthenticated or low-trust users.
Exploitation context
The source bundle does not show CISA KEV listing or any cited active exploitation. Exploitability and impact are not fully documented here.
Researcher notes
The CVE data is sparse: no CVSS, CWE, CPE, exploit status, or detailed remediation text beyond the before-3.4.1 version boundary. Avoid assuming remote code execution without confirming server behavior, plugin configuration, and vendor release details.
Mitigation direction
- Identify all WordPress sites using wp-file-upload.
- Update wp-file-upload to version 3.4.1 or later after confirming vendor guidance.
- Restrict upload forms to trusted users where business allows.
- Review web server handling of uploaded files and script execution.
- Check plugin configuration for permitted extensions and storage location.
Validation and detection
- Confirm installed wp-file-upload version on each WordPress site.
- Verify whether any public upload form uses the plugin.
- Review uploaded-file directories for unexpected .php.js files.
- Check web server logs for unusual upload activity.
- Document findings where the plugin is absent or already updated.
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-9341 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.