JEXTN FAQ Pro Extension 4.0.0 on Joomla ID sql injection

Summaryinfo

A vulnerability was found in JEXTN FAQ Pro Extension 4.0.0 on Joomla. It has been rated as critical. This affects an unknown part. Performing a manipulation of the argument ID as part of Parameter results in sql injection. This vulnerability is cataloged as CVE-2017-17875. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.

Detailsinfo

A vulnerability classified as critical has been found in JEXTN FAQ Pro Extension 4.0.0 on Joomla (Joomla Component). This affects an unknown function. The manipulation of the argument id as part of a Parameter 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, integrity, and availability. The summary by CVE is:

The JEXTN FAQ Pro extension 4.0.0 for Joomla! has SQL Injection via the id parameter in a view=category action.

The bug was discovered 12/26/2017. The weakness was shared 12/27/2017 as EDB-ID 43393 as not defined exploit (Exploit-DB). The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2017-17875 since 12/23/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.

After immediately, there has been an exploit disclosed. The exploit is shared for download 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 $0-$5k.

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

The vulnerability is also documented in the vulnerability database at Exploit-DB (43393). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Joomla Component

Name

• JEXTN FAQ Pro Extension

Version

• 4.0.0

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion