WordPress 2.3.0-4.7.4 - Authenticated SQL injection

Sign up to our free email alerts service for instant vulnerability notifications!

Description
Due bad solution of the database abstraction library WordPress exposes itself towards SQL Injection and validation bypass. Beside WordPress itself this issue have huge impact towards complete WP ecosystem.

Up to WordPress 4.8.1 is vulnerable, but this time attack is dependent from another plugins / themes / setup.

Affects WordPresses

fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5
fixed in version 4.7.5

References

URL https://medium.com/websec/wordpress-sqli-bbb2afcc8e94
URL https://wordpress.org/news/2017/09/wordpress-4-8-2-security-and-maintenance-release/
URL https://github.com/WordPress/WordPress/commit/70b21279098fc973eae803693c0705a548128e48
URL https://wpvulndb.com/vulnerabilities/8905

Classification

Type SQLI
OWASP Top 10 A1: Injection
CWE CWE-89

Miscellaneous

Submitter Slavco
Submitter Website https://medium.com/websec
Submitter Twitter mslavco
Views 896
Verified No
WPVDB ID 8906

Timeline

Publicly Published 2017-08-24 (2 months ago)
Added 2017-09-20 (about 1 month ago)
Last Updated 2017-09-20 (about 1 month ago)

Copyright & License

Copyright All data and resources contained within this page and this web site is Copyright © The WPScan Team.
License Some of this data may be used for non-commercial purposes, however, any potential commercial usage of this data will require a license. If you would like to inquire about a commercial license please contact us.