Joomshaper SP Movie Database 1.3 GET Request searchword sql injection

Summaryinfo

A vulnerability has been found in Joomshaper SP Movie Database 1.3 and classified as critical. Affected by this issue is some unknown functionality of the component GET Request Handler. Performing a manipulation of the argument searchword results in sql injection. This vulnerability is reported as CVE-2017-20266. The attack is possible to be carried out remotely. Moreover, an exploit is present.

Detailsinfo

A vulnerability was found in Joomshaper SP Movie Database 1.3. It has been classified as critical. This affects an unknown part of the component GET Request Handler. The manipulation of the argument searchword 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 SP Movie Database 1.3 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the searchword parameter. Attackers can send GET requests to the searchresults view with crafted SQL payloads in the searchword parameter to extract sensitive database information.

The weakness was disclosed by Ihsan Sencan as 42502. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2017-20266 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.

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 (42502). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Joomshaper

Name

• SP Movie Database

Version

• 1.3

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