Security readout for executives and security teams
Plain-English summary
This CVE covers an SQL injection in the WordPress wp-polls plugin before 2.72. A vulnerable public website could allow attacker-supplied input to affect database queries. The source bundle does not provide CVSS, exploit details, or confirmed real-world abuse.
Executive priority
Prioritize public WordPress sites using wp-polls, because SQL injection can threaten site data and integrity. Urgency is hard to quantify from the bundle because severity, exploitability, and active exploitation evidence are missing.
Technical view
CVE-2015-9352 describes SQL injection in wp-polls for WordPress before version 2.72. The bundle does not identify the vulnerable parameter, authentication requirement, CVSS vector, CWE, or exact affected CPEs. Treat validation as inventory-first unless vendor guidance provides more detail.
Likely exposure
Likely exposed systems are WordPress installations running the wp-polls plugin earlier than 2.72, especially public sites where visitors can interact with polls. The bundle does not define hosting model, CPEs, or deployment conditions, so exposure must be confirmed from plugin inventory.
Exploitation context
The provided KEV flag is false, and the bundle includes no cited evidence of active exploitation or public exploit availability. Because this is SQL injection in a WordPress plugin, internet-facing sites should still be prioritized for version verification.
Researcher notes
The source bundle is sparse: no CVSS, CWE, CPEs, vulnerable parameter, authentication context, or patch notes beyond the version boundary. Use vendor documentation and controlled testing to validate exposure; do not assume exploitability details from this record alone.
Mitigation direction
- Update wp-polls to version 2.72 or later where supported.
- Check the WordPress plugin developer page for current vendor guidance.
- Disable or remove wp-polls if an update cannot be applied promptly.
- Back up the site and database before plugin changes.
- Review compensating controls for public WordPress form inputs.
Validation and detection
- Inventory WordPress sites for installed wp-polls plugin versions.
- Confirm no production instance runs wp-polls earlier than 2.72.
- Review application and database logs for unusual poll-related errors.
- Verify the plugin update succeeded in WordPress admin or deployment records.
- Document any exception with owner, exposure, and remediation date.
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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2015-9352 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-polls/#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.