Security readout for executives and security teams
Plain-English summary
This CVE is a SQL injection in the WP-Testimonials WordPress plugin version 3.4.1. An authenticated user could make the plugin send unintended SQL to the site database. For an exposed WordPress site using this plugin, the business concern is possible database access or tampering through a logged-in account.
Executive priority
Prioritize this where the plugin is installed on production or customer-facing WordPress sites. The issue requires authentication, but SQL injection can threaten database confidentiality and integrity, and public exploit material increases urgency.
Technical view
CVE-2017-9418 describes SQL injection through the testid parameter to wp-admin/admin.php in WP-Testimonials 3.4.1. The CVE text says authenticated access is required and arbitrary SQL commands are possible. No CVSS score, CWE mapping, fixed version, or vendor mitigation is provided in the supplied bundle.
Likely exposure
Likely exposure is limited to WordPress installations running WP-Testimonials 3.4.1 with authenticated users able to reach wp-admin/admin.php. The bundle does not prove other versions or products are affected.
Exploitation context
The source bundle includes an Exploit-DB reference, so public exploit information exists. It does not show CISA KEV listing or evidence of active exploitation in the wild.
Researcher notes
The public bundle is sparse: it identifies the vulnerable parameter, plugin version, authentication requirement, and arbitrary SQL impact, but lacks CVSS, CWE, patch status, and confirmed exploitation status. Do not broaden affected versions without vendor evidence.
Mitigation direction
- Inventory WordPress sites for WP-Testimonials version 3.4.1.
- Check vendor or WPVulnDB guidance for a fixed release or recommended remediation.
- Disable or replace the plugin if no trustworthy fix is available.
- Limit WordPress admin access to necessary trusted users only.
- Review database backups and recovery readiness for affected sites.
Validation and detection
- Confirm whether WP-Testimonials is installed and record its exact version.
- Verify whether authenticated users can access the affected admin plugin path.
- Review WordPress user accounts for unnecessary or stale access.
- Check web and application logs for unusual authenticated plugin activity.
- Review database audit logs for unexpected changes if available.
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-2017-9418 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://wpvulndb.com/vulnerabilities/8845CVE reference · x_refsource_MISC
- 42166CVE reference · exploit, x_refsource_EXPLOIT-DB
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.