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.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
| Link | Tags |
|---|---|
| https://www.debian.org/security/2017/dsa-3997 | vendor advisory |
| https://medium.com/websec/wordpress-sqli-poc-f1827c20bf8e | third party advisory exploit |
| http://www.securityfocus.com/bid/100912 | vdb entry third party advisory |
| http://www.securitytracker.com/id/1039553 | vdb entry |
| https://github.com/WordPress/WordPress/commit/fc930d3daed1c3acef010d04acc2c5de93cd18ec | issue tracking third party advisory patch |
| https://core.trac.wordpress.org/changeset/41470 | patch vendor advisory |
| https://core.trac.wordpress.org/changeset/41496 | patch vendor advisory |
| https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/ | release notes patch vendor advisory |
| https://medium.com/websec/wordpress-sqli-bbb2afcc8e94 | exploit third party advisory mitigation |
| https://github.com/WordPress/WordPress/commit/70b21279098fc973eae803693c0705a548128e48 | issue tracking third party advisory patch |