CVE-2017-16510
Last modified
CVE-2017-16510 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 7.74% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Wordpress | Wordpress | <= 4.8.2 |
References
- http://www.securityfocus.com/bid/101638Third Party Advisory, VDB Entry
- https://blog.ircmaxell.com/2017/10/disclosure-wordpress-wpdb-sql-injection-technical.htmlIssue Tracking, Third Party Advisory
- https://codex.wordpress.org/Version_4.8.3Issue Tracking, Vendor Advisory
- https://github.com/WordPress/WordPress/commit/a2693fd8602e3263b5925b9d799ddd577202167dIssue Tracking, Patch, Vendor Advisory
- https://wordpress.org/news/2017/10/wordpress-4-8-3-security-release/Issue Tracking, Vendor Advisory
- https://wpvulndb.com/vulnerabilities/8941Issue Tracking, Vendor Advisory
- http://www.securityfocus.com/bid/101638Third Party Advisory, VDB Entry
- https://blog.ircmaxell.com/2017/10/disclosure-wordpress-wpdb-sql-injection-technical.htmlIssue Tracking, Third Party Advisory
- https://codex.wordpress.org/Version_4.8.3Issue Tracking, Vendor Advisory
- https://github.com/WordPress/WordPress/commit/a2693fd8602e3263b5925b9d799ddd577202167dIssue Tracking, Patch, Vendor Advisory
- https://wordpress.org/news/2017/10/wordpress-4-8-3-security-release/Issue Tracking, Vendor Advisory
- https://wpvulndb.com/vulnerabilities/8941Issue Tracking, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-16510?
How severe is CVE-2017-16510?
How do I fix CVE-2017-16510?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-16505Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-16506Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-16507Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-16508Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-16509Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-1651IBM Rational Quality Manager and IBM Rational Collaborative …5.4
- CVE-2017-16512The vagrant update process in Hashicorp vagrant-vmware-fusio…
- CVE-2017-16513Ipswitch WS_FTP Professional before 12.6.0.3 has buffer over…
- CVE-2017-16514Multiple persistent stored Cross-Site-Scripting (XSS) vulner…
- CVE-2017-16516In the yajl-ruby gem 1.3.0 for Ruby, when a crafted JSON fil…7.5
- CVE-2017-1652IBM Rational Quality Manager and IBM Rational Collaborative …5.4
- CVE-2017-16520Inedo BuildMaster before 5.8.2 does not properly restrict cr…
Are you affected by CVE-2017-16510?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
