CVE-2017-16510

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-14. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 8%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
93.9%
KEV
Not listed

Published

November 2, 2017

Last Modified

May 13, 2026

Advisory Details (7)

Auto-updated May 15, 2026
🔬 Proof of concept available. Patch available.
generic🟡 PoC Available

Disclosure: WordPress WPDB SQL Injection - Technical | ircmaxell's Blog

https://blog.ircmaxell.com/2017/10/disclosure-wordpress-wpdb-sql-injection-technical.html
generic
http://www.securityfocus.com/bid/101638
generic

[SECURITY] [DSA 4090-1] wordpress security update

https://www.debian.org/security/2018/dsa-4090
generic

WordPress 4.8.3 Security Release – WordPress News

https://wordpress.org/news/2017/10/wordpress-4-8-3-security-release/
generic Patch Available

[SECURITY] [DLA 1160-1] wordpress security update

https://lists.debian.org/debian-lts-announce/2017/11/msg00003.html
generic

Database: Restore numbered placeholders in `wpdb::prepare()`. · WordPress/WordPress@a2693fd · GitHub

https://github.com/WordPress/WordPress/commit/a2693fd8602e3263b5925b9d799ddd577202167d
generic

Version 4.8.3 – Documentation – WordPress.org

https://codex.wordpress.org/Version_4.8.3

Data Freshness Timeline

(refreshed 9× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 02:20 UTCEPSS rescore
  4. 2026-07-05 02:27 UTCEPSS rescore
  5. 2026-07-04 06:28 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-07-01 15:02 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-29 14:03 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-25 13:47 UTCEPSS rescore
  16. 2026-06-24 14:02 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-22 14:23 UTCEPSS rescore
  20. 2026-06-21 14:54 UTCEPSS rescore
  21. 2026-06-21 14:54 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-19 17:55 UTCOSV refresh
  25. 2026-06-18 17:50 UTCEPSS rescore
Show 55 more
  1. 2026-06-17 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-13 22:57 UTCEPSS rescore
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-11 13:57 UTCEPSS rescore
  7. 2026-06-10 22:15 UTCEPSS rescore
  8. 2026-06-08 14:14 UTCEPSS rescore
  9. 2026-06-05 22:44 UTCEPSS rescore
  10. 2026-06-05 06:08 UTCEPSS rescore
  11. 2026-06-05 06:08 UTCEPSS rescore
  12. 2026-06-04 13:10 UTCEPSS rescore
  13. 2026-06-04 13:10 UTCEPSS rescore
  14. 2026-06-02 20:11 UTCEPSS rescore
  15. 2026-06-02 20:11 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-05-31 22:28 UTCEPSS rescore
  19. 2026-05-31 00:14 UTCEPSS rescore
  20. 2026-05-30 23:23 UTCOSV refresh
  21. 2026-05-29 13:41 UTCEPSS rescore
  22. 2026-05-28 13:42 UTCEPSS rescore
  23. 2026-05-28 13:42 UTCEPSS rescore
  24. 2026-05-27 13:38 UTCEPSS rescore
  25. 2026-05-27 13:38 UTCEPSS rescore
  26. 2026-05-26 07:17 UTCEPSS rescore
  27. 2026-05-26 07:17 UTCEPSS rescore
  28. 2026-05-22 21:15 UTCEPSS rescore
  29. 2026-05-22 21:15 UTCEPSS rescore
  30. 2026-05-22 21:15 UTCEPSS rescore
  31. 2026-05-20 22:37 UTCEPSS rescore
  32. 2026-05-20 22:37 UTCEPSS rescore
  33. 2026-05-20 11:21 UTCEPSS rescore
  34. 2026-05-20 11:21 UTCEPSS rescore
  35. 2026-05-20 09:12 UTCEG score recompute
  36. 2026-05-20 09:12 UTCGHSA enrichment
  37. 2026-05-20 05:27 UTCEG score recompute
  38. 2026-05-20 05:27 UTCGHSA enrichment
  39. 2026-05-20 01:42 UTCEG score recompute
  40. 2026-05-20 01:42 UTCGHSA enrichment
  41. 2026-05-19 21:57 UTCEG score recompute
  42. 2026-05-19 21:57 UTCGHSA enrichment
  43. 2026-05-19 18:12 UTCEG score recompute
  44. 2026-05-19 18:12 UTCGHSA enrichment
  45. 2026-05-19 14:27 UTCEG score recompute
  46. 2026-05-19 14:27 UTCGHSA enrichment
  47. 2026-05-19 10:42 UTCEG score recompute
  48. 2026-05-19 10:42 UTCGHSA enrichment
  49. 2026-05-19 06:56 UTCEG score recompute
  50. 2026-05-19 06:56 UTCGHSA enrichment
  51. 2026-05-19 03:11 UTCEG score recompute
  52. 2026-05-19 03:11 UTCGHSA enrichment
  53. 2026-05-18 23:24 UTCEG score recompute
  54. 2026-05-18 21:30 UTCEPSS rescore
  55. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-16510?
CVE-2017-16510 is a critical vulnerability published on November 2, 2017. 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.
When was CVE-2017-16510 disclosed?
CVE-2017-16510 was first published in the National Vulnerability Database on November 2, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-16510 actively exploited?
CVE-2017-16510 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 93.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-16510?
CVE-2017-16510 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2017-16510?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-16510, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-16510

Explore →

Is Your Infrastructure Affected by CVE-2017-16510?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs