Joomlathat Calendar Planner 1.0.1 GET Request category_id sql injection

Summaryinfo

A vulnerability was found in Joomlathat Calendar Planner 1.0.1 and classified as critical. This affects an unknown part of the component GET Request Handler. Executing a manipulation of the argument category_id can lead to sql injection. This vulnerability appears as CVE-2017-20267. The attack may be performed from remote. In addition, an exploit is available.

Detailsinfo

A vulnerability was found in Joomlathat Calendar Planner 1.0.1. It has been declared as critical. This vulnerability affects an unknown code of the component GET Request Handler. The manipulation of the argument category_id with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Joomla! Component Calendar Planner 1.0.1 contains an SQL injection vulnerability that allows unauthenticated attackers to inject SQL commands through the category_id parameter. Attackers can send GET requests to the events view with malicious SQL code in the category_id parameter to extract sensitive database information.

The weakness was presented by Ihsan Sencan as 42501. The advisory is available at exploit-db.com. This vulnerability was named CVE-2017-20267 since 06/19/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details and also a public exploit are known. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.

It is possible to download the exploit at exploit-db.com. It is declared as proof-of-concept.

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 (42501). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

• Calendar Software

Vendor

• Joomlathat

Name

• Calendar Planner

Version

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