Before version 4.8.2, WordPress mishandled % characters and additional placeholder values in $wpdb->prepare, and thus did not properly address the possibility of plugins and themes enabling SQL injection attacks.
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is in WordPress's database layer: before version 4.8.2, the $wpdb->prepare function mishandled % characters and additional placeholder values, so it did not properly guard against SQL injection in plugins and themes that use it. An attacker able to supply input to a plugin or theme that relies on $wpdb->prepare could potentially inject SQL.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 4 years after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+4 yrs
Patch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.
2 related vulnerabilities in the same code over 6 weeks.
Linked vulnerabilitiesLinked by evidence that a fix failed or the same code was patched again. Oldest first.
- This CVECVE-2017-14723Before version 4.8.2, WordPress mishandled % characters and…23 Sep 2017
relatedMedium
Why these are linked: Link confidenceHow strong the evidence is that two CVEs are related. High: stated in the CVE text or linked in an advisory, or the same code was patched one release apart. Medium: the same code, or a version step plus a similar description. Low: similar description only.
- Same code patched: wp-db.php (machine-matched)Functions: preparecommit fc930d3commit 70b2127commit a2693fd