Store Locator Plugin up to 3.11 on WordPress sl-xml.php sl_custom_field sql injection

Summaryinfo

A vulnerability classified as critical has been found in Store Locator Plugin up to 3.11 on WordPress. This impacts an unknown function of the file sl-xml.php. The manipulation of the argument sl_custom_field as part of Parameter leads to sql injection. This vulnerability is uniquely identified as CVE-2014-8621. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in Store Locator Plugin up to 3.11 on WordPress (WordPress Plugin) and classified as critical. This issue affects some unknown processing of the file sl-xml.php. The manipulation of the argument sl_custom_field as part of a Parameter 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. The summary by CVE is:

SQL injection vulnerability in the Store Locator plugin 2.3 through 3.11 for WordPress allows remote attackers to execute arbitrary SQL commands via the sl_custom_field parameter to sl-xml.php.

The bug was discovered 10/27/2014. The weakness was disclosed 10/16/2017 (Website). The advisory is shared at g0blin.co.uk. The identification of this vulnerability is CVE-2014-8621 since 11/04/2014. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.

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

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

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

Productinfo

Type

• WordPress Plugin

Name

• Store Locator Plugin

Version

• 3.0
• 3.1
• 3.2
• 3.3
• 3.4
• 3.5
• 3.6
• 3.7
• 3.8
• 3.9
• 3.10
• 3.11

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