thiagosf Skitter Slideshow Plugin up to 2.5.2 on WordPress /image.php server-side request forgery

Summaryinfo

A vulnerability marked as critical has been reported in thiagosf Skitter Slideshow Plugin up to 2.5.2 on WordPress. Affected by this issue is some unknown functionality of the file /image.php. This manipulation causes server-side request forgery. This vulnerability is tracked as CVE-2022-1751. The attack is possible to be carried out remotely. No exploit exists.

Detailsinfo

A vulnerability was found in thiagosf Skitter Slideshow Plugin up to 2.5.2 on WordPress. It has been declared as critical. Affected by this vulnerability is an unknown code of the file /image.php. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The Skitter Slideshow plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 2.5.2 via the /image.php file. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services.

The weakness was disclosed by Bartu Utku Sarp. The advisory is shared at wordfence.com. This vulnerability is known as CVE-2022-1751 since 05/17/2022. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 08/17/2024).

By approaching the search of inurl:image.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.

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

Productinfo

Type

• WordPress Plugin

Vendor

• thiagosf

Name

• Skitter Slideshow Plugin

Version

• 2.5.0
• 2.5.1
• 2.5.2

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