Post Indexer Plugin 3.0.6.1 on WordPress classes/class.model.php sql injection

Summaryinfo

A vulnerability, which was classified as critical, has been found in Post Indexer Plugin 3.0.6.1 on WordPress. This affects an unknown part of the file classes/class.model.php. The manipulation leads to sql injection. It is possible to initiate the attack remotely. There is no exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Post Indexer Plugin 3.0.6.1 on WordPress (WordPress Plugin). It has been rated as critical. This issue affects an unknown functionality of the file classes/class.model.php. 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.

The bug was discovered 11/01/2016. The weakness was shared 11/17/2016 by Glyn Wintle as SQL Injection in Post Indexer allows super admins to read the contents of the database (WordPress plugin) as confirmed mailinglist post (Full-Disclosure). The advisory is shared at seclists.org. The vendor cooperated in the coordination of the public release. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue. The advisory points out:

Post Indexer does not use prepared queries in many cases and in some of its database calls it uses backticks (`). These are not automatically escaped by WordPress, thus leading to the possibility of SQL injection. In other places in the code it simply takes user controlled values and adds them to SQL queries.

The vulnerability was handled as a non-public zero-day exploit for at least 16 days. During that time the estimated underground price was around $0-$5k. By approaching the search of inurl:classes/class.model.php it is possible to find vulnerable targets with Google Hacking. The advisory illustrates:

To exploit this vulnerability you need to be a super admin.

Upgrading to version 3.0.6.2 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.

security.dxw.com is providing further details. The entry VDB-93690 is related to this item. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Type

• WordPress Plugin

Name

• Post Indexer Plugin

Version

• 3.0.6.1

CPE 2.3info

• 🔍

CPE 2.2info

• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion