Security readout for executives and security teams
Plain-English summary
CVE-2015-9358 describes a cross-site scripting issue in the FeedWordPress plugin for WordPress before version 2015.0514. A vulnerable site could expose users to unwanted script execution in a browser. The public data is sparse and does not provide CVSS, CWE, or confirmed exploitation.
Executive priority
Prioritize this as an inventory and cleanup item, not a confirmed emergency. Remediate promptly if FeedWordPress is present on public or business-critical WordPress sites, especially older installations that may have accumulated unpatched plugins.
Technical view
The issue is reported as XSS in FeedWordPress before 2015.0514, associated with WordPress add_query_arg() and remove_query_arg() usage. The source bundle does not identify a CVSS score, CWE, exploitability details, or affected CPEs. Treat exposure as version-dependent on plugin presence.
Likely exposure
WordPress sites using the FeedWordPress plugin before version 2015.0514 are the likely exposed population. The CVE metadata lists affected vendor and product as n/a, so asset confirmation must come from local WordPress plugin inventory.
Exploitation context
No CISA KEV listing is provided, and the supplied sources do not state active exploitation or provide exploit maturity. The public record only supports that an XSS vulnerability existed before the named plugin version.
Researcher notes
The record is thin: no CVSS, CWE, CPEs, or exploit-status evidence is included. The key technical fact is XSS in FeedWordPress before 2015.0514 via add_query_arg() and remove_query_arg(). Avoid assuming broader WordPress core exposure from this CVE alone.
Mitigation direction
- Inventory all WordPress sites for the FeedWordPress plugin.
- Upgrade FeedWordPress to version 2015.0514 or later where still used.
- Disable or remove the plugin where it is not required.
- Check the WordPress plugin page and vendor guidance for current maintenance status.
- Apply normal WordPress hardening and least-privilege admin practices.
Validation and detection
- Confirm each WordPress instance has FeedWordPress absent or at version 2015.0514 or later.
- Review plugin changelog information on the WordPress developers page.
- Check web logs for suspicious requests targeting FeedWordPress-related paths or parameters.
- Confirm no unsupported legacy WordPress instances still run the plugin.
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-9358 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/feedwordpress/#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.