WordPress component: SQL injection
WordPress component is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
- Component
- WordPress component
- Plugin slug
- Not applicable
- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Nov 02, 2017
Update, patch or deactivate.
Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
WordPress before 4.8.3 is affected by an issue where $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi) in plugins and themes, as demonstrated by a "double prepare" approach, a different vulnerability than CVE-2017-14723.
NVD vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary and upstream sources
- NVD record for CVE-2017-16510
- Upstream reference securityfocus.com
- Upstream reference blog.ircmaxell.com
- WordPress upstream reference codex.wordpress.org
- GitHub upstream reference github.com
- Upstream reference lists.debian.org
- WordPress upstream reference wordpress.org
- Upstream reference wpvulndb.com
- Upstream reference debian.org
- Upstream reference securityfocus.com
- Upstream reference blog.ircmaxell.com
- WordPress upstream reference codex.wordpress.org
- GitHub upstream reference github.com
- Upstream reference lists.debian.org
- WordPress upstream reference wordpress.org
- Upstream reference wpvulndb.com
- Upstream reference debian.org