CVE-2017-16510 in the critical feed json
WordPress before 4.8.3 is affected by an issue where $wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL inj…
published 2017-11-02 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-7704
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.7%
- EPSS 6.7% chance of exploitation in 30 days, percentile 93%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- wordpress Debian 14, Debian 13, Debian 12 4.8.3+dfsg-1
debian advisories DEBIAN-CVE-2017-16510
Exploit prediction
6.70% chance of exploitation in the next 30 days, higher than 93% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
- Technology feeds
References
-
github.com
/WordPress/WordPress/commit/a2693fd8602e3263b5925b9d799ddd577202167d
issue-tracking, patch, vendor-advisory
-
debian.org
/security/2018/dsa-4090
vendor-advisory
-
wpvulndb.com
/vulnerabilities/8941
issue-tracking, vendor-advisory
-
codex.wordpress.org
/Version_4.8.3
issue-tracking, vendor-advisory
-
wordpress.org
/news/2017/10/wordpress-4-8-3-security-release/
issue-tracking, vendor-advisory
-
lists.debian.org
/debian-lts-announce/2017/11/msg00003.html
mailing-list
-
securityfocus.com
/bid/101638
vdb-entry, third-party-advisory
-
blog.ircmaxell.com
/2017/10/disclosure-wordpress-wpdb-sql-injection-technical.html
issue-tracking, third-party-advisory
Sources
- CVE List CVE-2017-16510
- NVD CVE-2017-16510
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.