Security readout for executives and security teams
Plain-English summary
This WordPress polling plugin can let a logged-in Administrator read sensitive database information through a crafted search value. The high privilege requirement limits the attacker pool, but compromise of an administrator account could expose WordPress data. The supplied sources identify versions through 2.4.6 as affected but do not confirm a fixed release.
Executive priority
Prioritize remediation on sites holding sensitive customer, employee, credential, or commercial data. Treat it as a moderate issue requiring prompt handling, with higher urgency where administrator-account security is uncertain or a privileged compromise is already suspected.
Technical view
CVE-2025-3470 is a CWE-89 SQL injection in the plugin’s "s" parameter. Insufficient input escaping and an inadequately prepared SQL query allow an authenticated Administrator-or-higher user to alter an existing query and extract database information. CVSS 3.1 is 4.9: network-accessible, low complexity, high privileges, no user interaction, with high confidentiality impact.
Likely exposure
Exposure is limited to WordPress installations running TS Poll version 2.4.6 or earlier where an attacker already has Administrator-level access. Risk increases where administrator accounts are numerous, shared, weakly protected, or previously compromised. The supplied evidence does not establish exposure for later versions.
Exploitation context
The source bundle does not provide evidence of active exploitation, and the CVE is not marked KEV. Exploitation requires authenticated Administrator-level access, making this more relevant as a post-account-compromise data-theft path than an unauthenticated initial-entry vulnerability.
Researcher notes
The cited WordPress Trac source points to administrative list-query handling in class-ts_poll_list.php. Available evidence supports database information extraction through SQL injection, but does not substantiate data modification, service disruption, unauthenticated exploitation, a confirmed fixed version, or exploitation in the wild.
Mitigation direction
- Inventory WordPress sites and identify TS Poll installations running version 2.4.6 or earlier.
- Check the plugin vendor’s current guidance for a confirmed fixed release or supported mitigation.
- Restrict Administrator access to essential trusted users and enforce strong authentication protections.
- If remediation is unavailable, consider disabling the plugin after assessing business impact.
Validation and detection
- Confirm the installed plugin version on every WordPress instance.
- Review Administrator accounts and remove unexpected, dormant, or unnecessary privileged access.
- Review relevant application and database logs for anomalous plugin search activity by administrators.
- Verify vendor-confirmed remediation is deployed before closing the finding.
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.
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupDatabase 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-2025-3470 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
- Medium
- CVSS
- 4.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N1.23.6WordfenceVulnerability scoring details
Base CVSS 3.1 score
4.9MediumVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- Source timelineWordfence
Discovered
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- Source timelineWordfence
Disclosed
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/1e2dab05-97ce-4f53-8069-2577c5c25b16?source=cveCVE reference, Wordfence
- https://plugins.trac.wordpress.org/browser/poll-wp/tags/2.4.6/admin/class-ts_poll_list.php#L27CVE reference, Wordfence
- https://mebroccoli.blogspot.com/2025/04/CVE-2025-3470.htmlCVE reference, Wordfence
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.
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.