nextgeneditor NextGen Editor 2.1.0 GET Request index.php plname sql injection

Summaryinfo

A vulnerability was found in nextgeneditor NextGen Editor 2.1.0. It has been classified as critical. Affected by this vulnerability is an unknown functionality of the file index.php of the component GET Request Handler. Performing a manipulation of the argument plname results in sql injection. This vulnerability is known as CVE-2017-20252. Remote exploitation of the attack is possible. Furthermore, an exploit is available.

Detailsinfo

A vulnerability, which was classified as critical, was found in nextgeneditor NextGen Editor 2.1.0. This affects an unknown code block of the file index.php of the component GET Request Handler. The manipulation of the argument plname 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, integrity, and availability. The summary by CVE is:

Joomla NextGen Editor 2.1.0 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL commands through the plname parameter. Attackers can send GET requests to index.php with option=com_nge&view=config and inject malicious SQL code in the plname parameter to extract sensitive database information.

The weakness was published by Ihsan Sencan as 43365. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2017-20252 since 06/19/2026. 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.

The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. By approaching the search of inurl:index.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.

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

Productinfo

Vendor

• nextgeneditor

Name

• NextGen Editor

Version

• 2.1.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