CVE-2023-49852

Responsive Slick Slider WordPress <= 1.5 - Authenticated (Contributor+) Content Injection

2023-12-07 00:00
Abdi Pranata

Strategic Overview

Status
Unpatched
Affected Version
<= 1.5
CVSS
4.3Medium
Weakness type
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
CVE
CVE-2023-49852
View all Responsive Slick Slider WordPress vulnerabilities

At a glance

CVE-2023-49852 is a medium-severity Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the Responsive Slick Slider WordPress WordPress plugin, affecting versions <= 1.5. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2023, reported by Abdi Pranata.

Vulnerability Overview

The Responsive Slick Slider WordPress plugin for WordPress is vulnerable to content injection in all versions up to, and including, 1.5. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary content.

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 interaction from a victim user.

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

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