Security readout for executives and security teams
Plain-English summary
This is a cross-site scripting issue in the WordPress content-grabber plugin 1.0. A vulnerable site may let malicious script content run in a user's browser through plugin fields. The public record is sparse and has no CVSS score, so urgency depends on whether the plugin is installed and reachable.
Executive priority
Treat this as inventory-driven. It is not KEV-listed and severity is not scored, but public WordPress plugin XSS can create account and content integrity risk if the vulnerable plugin is present.
Technical view
CVE-2015-9469 describes XSS in content-grabber plugin 1.0 for WordPress through obj_field_name or obj_field_id. The source bundle provides no CVSS, CWE, CPE, or confirmed affected-version range beyond 1.0.
Likely exposure
Likely limited to WordPress installations that have the content-grabber plugin version 1.0 installed or retained. The CVE metadata does not provide CPEs, broader affected versions, or hosting details, so exposure should be confirmed by plugin inventory.
Exploitation context
The bundle has no CISA KEV listing and no cited evidence of active exploitation. Packet Storm is listed as a public disclosure reference, which means technical details were public, but the provided bundle does not establish real-world exploitation.
Researcher notes
The public CVE record is thin: no CVSS, CWE, CPEs, or remediation details are provided. Validate exposure against local WordPress plugin inventory and the referenced plugin and Packet Storm pages without assuming broader affected versions.
Mitigation direction
- Inventory WordPress sites for the content-grabber plugin and version 1.0.
- Disable or remove the plugin where it is not business-critical.
- Check the WordPress plugin page and vendor guidance for available updates or retirement status.
- Prioritize remediation on public or authenticated-user-facing WordPress sites.
- Review compensating controls for XSS detection and script injection blocking.
Validation and detection
- Confirm whether content-grabber 1.0 is installed on any WordPress instance.
- Verify whether any later vendor-supported plugin version is available.
- Review application logs for unusual obj_field_name or obj_field_id values.
- Check whether affected plugin functionality is reachable by untrusted users.
- Document instances where the plugin is absent to close exposure tracking.
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-9469 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/content-grabber/#developersCVE reference · x_refsource_MISC
- https://packetstormsecurity.com/files/132910/CVE 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.