WordPress up to 1.5.1.2 RPC Server HTTP_RAW_POST_DATA 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.
6.6$0-$5k0.00

Summaryinfo

A vulnerability labeled as critical has been found in WordPress up to 1.5.1.2. The affected element is an unknown function of the component RPC Server. Such manipulation of the argument HTTP_RAW_POST_DATA leads to sql injection. This vulnerability is listed as CVE-2005-2108. The attack may be performed from remote. In addition, an exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in WordPress up to 1.5.1.2 (Content Management System). It has been rated as critical. Affected by this issue is an unknown part of the component RPC Server. The manipulation of the argument HTTP_RAW_POST_DATA 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:

SQL injection vulnerability in XMLRPC server in WordPress 1.5.1.2 and earlier allows remote attackers to execute arbitrary SQL commands via input that is not filtered in the HTTP_RAW_POST_DATA variable, which stores the data in an XML file.

The bug was discovered 06/28/2005. The weakness was presented 06/29/2005 (Website). The advisory is available at secunia.com. This vulnerability is handled as CVE-2005-2108 since 07/01/2005. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details as well as a public exploit are known. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.

After even before and not, there has been an exploit disclosed. The exploit is available at exploit-db.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 18601 (WordPress < 1.5.1.3 XMLRPC SQL Injection), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses and running in the context r.

Upgrading eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at Exploit-DB (1077), Tenable (18601), OSVDB (17637†), Secunia (SA15831†) and Vulnerability Center (SBV-8714†). See VDB-25660, VDB-25659 and VDB-25657 for similar entries. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 6.6

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

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: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 18601
Nessus Name: WordPress < 1.5.1.3 XMLRPC SQL Injection
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 54000
OpenVAS Name: FreeBSD Ports: wordpress
OpenVAS File: 🔍
OpenVAS Family: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Timelineinfo

06/28/2005 🔍
06/29/2005 +1 days 🔍
06/29/2005 +0 days 🔍
06/29/2005 +0 days 🔍
06/30/2005 +0 days 🔍
06/30/2005 +0 days 🔍
06/30/2005 +0 days 🔍
07/01/2005 +0 days 🔍
07/01/2005 +0 days 🔍
07/05/2005 +4 days 🔍
07/25/2005 +20 days 🔍
03/11/2015 +3516 days 🔍
06/07/2019 +1549 days 🔍

Sourcesinfo

Product: wordpress.com

Advisory: secunia.com⛔
Status: Not defined

CVE: CVE-2005-2108 (🔍)
GCVE (CVE): GCVE-0-2005-2108
GCVE (VulDB): GCVE-100-25658
Secunia: 15831 - Wordpress Multiple Vulnerabilities, Moderately Critical
OSVDB: 17637 - WordPress XMLRPC Multiple Method SQL Injection
Vulnerability Center: 8714 - SQL Injection in XMLRPC Server in WordPress <= 1.5.1.2 via HTTP_RAW_POST_DATA Variable, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 03/11/2015 11:41
Updated: 06/07/2019 17:20
Changes: 03/11/2015 11:41 (78), 06/07/2019 17:20 (3)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!