Post Indexer Plugin 3.0.6.1 on WordPress cron.postindexerrebuild.php sql injection

Summaryinfo

A vulnerability, which was classified as critical, was found in Post Indexer Plugin 3.0.6.1 on WordPress. This vulnerability affects unknown code of the file classes/cron.postindexerrebuild.php. The manipulation results in sql injection. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical has been found in Post Indexer Plugin 3.0.6.1 on WordPress (WordPress Plugin). Affected is some unknown functionality of the file classes/cron.postindexerrebuild.php. The manipulation with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as 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. This is going to have an impact on confidentiality.

The bug was discovered 11/01/2016. The weakness was published 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 available at seclists.org. The public release has been coordinated with the vendor. The exploitability is told to be easy. It is possible to launch the attack remotely. A authentication is required for exploitation. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project. 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/cron.postindexerrebuild.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.

Further details are available at security.dxw.com. Similar entry is available at VDB-93689. If you want to get best quality of vulnerability data, you may have to visit VulDB.

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

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

Discussion