CVE-2021-24913

Logo Showcase with Slick Slider <= 2.0 - Cross-Site Request Forgery

2022-01-31 00:00
apple502j

Strategic Overview

Status
Patched in 2.0.1
Affected Version
< 2.0.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2021-24913
View all Logo Showcase – Responsive Logo Carousel, Logo Slider & Logo Grid vulnerabilities

At a glance

CVE-2021-24913 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Logo Showcase WordPress plugin, affecting versions < 2.0.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.1; sites on affected versions should update now. Disclosed January 2022, reported by apple502j.

Vulnerability Overview

The Logo Showcase with Slick Slider plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.0. This is due to missing or incorrect nonce validation on the lswss_save_attachment_data AJAX action. This makes it possible for unauthenticated attackers to change the title, description, alt text, and URL of arbitrary uploaded media via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Logo Showcase < 2.0.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Logo Showcase the fix is 2.0.1: builds < 2.0.1 are affected, anything from 2.0.1 onward is not.

Remediation

Update to version 2.0.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Logo Showcase: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Logo Showcase 2.0.1 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C