Security readout for executives and security teams
Plain-English summary
CVE-2015-9338 affects the WordPress wp-file-upload plugin before version 2.5.0. The reported issue is weak restriction of .php uploads. On a typical WordPress server, allowing PHP files into web-accessible areas can create serious site compromise risk, but the provided sources do not confirm exploitation details.
Executive priority
Prioritize remediation for public WordPress sites using this plugin, especially where file uploads are enabled. The business risk is potential website takeover, but available evidence lacks severity scoring and confirmed exploitation.
Technical view
The CVE record describes insufficient restrictions on upload of .php files in wp-file-upload before 2.5.0. No CVSS, CWE, authentication requirements, route details, or proof of active exploitation are provided in the bundle. KEV status is false, so exploitation should not be described as confirmed from these sources.
Likely exposure
Exposure is likely limited to WordPress sites with wp-file-upload installed below version 2.5.0. The bundle does not identify affected configurations, required permissions, or whether uploads are publicly executable.
Exploitation context
The sources do not report active exploitation and the CVE is not marked KEV. Risk comes from the class of issue: uploaded PHP may become executable if stored in a web-served path on a PHP-enabled host.
Researcher notes
Key missing details include authentication context, vulnerable endpoint, storage path, default configuration impact, and fixed-version changelog specifics. Treat conclusions beyond the version boundary and file type restriction as inference, not confirmed fact.
Mitigation direction
- Inventory WordPress sites for wp-file-upload installations and versions.
- Upgrade wp-file-upload to version 2.5.0 or later where available.
- Disable or remove the plugin if it cannot be updated.
- Review server controls that prevent PHP execution in upload directories.
- Check vendor plugin guidance before applying environment-specific mitigations.
Validation and detection
- Confirm plugin version from WordPress admin or asset inventory.
- Verify whether any site still runs wp-file-upload below 2.5.0.
- Review web server rules for PHP execution in upload locations.
- Inspect recent upload activity for unexpected PHP files.
- Document findings and remediation status per affected WordPress site.
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-9338 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.