cpe:/a:oturia:smart_google_code_inserter:1.0::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:2.0::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:2.1::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:2.2::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:3.0::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:3.1::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:3.2::~~~wordpress~~ cpe:/a:oturia:smart_google_code_inserter:3.4::~~~wordpress~~ CVE-2018-3811 2018-01-01T01:29:00.247-05:00 2018-01-16T13:39:22.920-05:00 7.5 NETWORK LOW NONE PARTIAL PARTIAL PARTIAL http://nvd.nist.gov 2018-01-16T12:37:27.340-05:00 EXPLOIT-DB 43420 MISC https://limbenjamin.com/articles/smart-google-code-inserter-auth-bypass.html MISC https://wordpress.org/plugins/smart-google-code-inserter/#developers MISC https://wpvulndb.com/vulnerabilities/8988 SQL Injection vulnerability in the Oturia Smart Google Code Inserter plugin before 3.5 for WordPress allows unauthenticated attackers to execute SQL queries in the context of the web server. The saveGoogleAdWords() function in smartgooglecode.php did not use prepared statements and did not sanitize the $_POST["oId"] variable before passing it as input into the SQL query.