WordPress up to 4.8.2 wpdb->prepare sql injection

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
8.4$0-$5k0.00

Summaryinfo

A vulnerability, which was classified as critical, was found in WordPress. This affects the function wpdb->prepare. Such manipulation leads to sql injection. This vulnerability is listed as CVE-2017-16510. The attack may be performed from remote. There is no available exploit. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in WordPress (Content Management System). It has been rated as critical. Affected by this issue is the function wpdb->prepare. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:

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.

The bug was discovered 11/02/2017. The weakness was presented 11/02/2017 by Anthony Ferrara (Website). The advisory is shared for download at securityfocus.com. This vulnerability is handled as CVE-2017-16510 since 11/02/2017. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1505.

The vulnerability scanner Nessus provides a plugin with the ID 104398 (Debian DLA-1160-1 : wordpress security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176269 (Debian Security Update for wordpress (DSA 4090-1)).

Upgrading to version 3.7.23, 3.8.23, 3.9.21, 4.0.20, 4.1.20, 4.2.17, 4.3.13, 4.4.12, 4.5.11, 4.6.8, 4.7.7 or 4.8.3 eliminates this vulnerability. The upgrade is hosted for download at github.com. A possible mitigation has been published 2 days after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Tenable (104398) and SecurityFocus (BID 101638†). blog.ircmaxell.com is providing further details. See VDB-110156, VDB-110157, VDB-110158 and VDB-110159 for similar entries. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.5
VulDB Meta Temp Score: 8.4

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 9.8
NVD Vector: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 104398
Nessus Name: Debian DLA-1160-1 : wordpress security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 100908
OpenVAS Name: WordPress esc_sql Function SQL Injection Vulnerability - Nov 2017 (Windows)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: WordPress 3.7.23/3.8.23/3.9.21/4.0.20/4.1.20/4.2.17/4.3.13/4.4.12/4.5.11/4.6.8/4.7.7/4.8.3
Patch: github.com

Timelineinfo

10/31/2017 🔍
11/02/2017 +2 days 🔍
11/02/2017 +0 days 🔍
11/02/2017 +0 days 🔍
11/02/2017 +0 days 🔍
11/02/2017 +0 days 🔍
11/04/2017 +2 days 🔍
11/06/2017 +2 days 🔍
01/05/2023 +1886 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: a2693fd8602e3263b5925b9d799ddd577202167d⛔
Researcher: Anthony Ferrara
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2017-16510 (🔍)
GCVE (CVE): GCVE-0-2017-16510
GCVE (VulDB): GCVE-100-108908

OVAL: 🔍

SecurityFocus: 101638 - WordPress 'wpdb::prepare()' Method SQL Injection Vulnerability

Misc.: 🔍
See also: 🔍

Entryinfo

Created: 11/02/2017 23:13
Updated: 01/05/2023 14:33
Changes: 11/02/2017 23:13 (81), 06/07/2020 18:53 (4), 01/05/2023 14:31 (5), 01/05/2023 14:33 (1)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!