WordPress security by component
LayerSlider
Plugin description
LayerSlider is a WordPress component with 5 published CVE records in this archive. The latest tracked vulnerability was published May 23, 2024; the highest CVE/CNA score is 9.8.
Plugin slug:
layersliderLatest vulnerability
CVE-2024-4575: LayerSlider: Cross-site scripting
LayerSlider is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
| Safe version |
|
||
|---|---|---|---|
| May 23, 2024 |
CVE-2024-4575
LayerSlider: Cross-site scripting
LayerSlider is affected by cross-site scripting. Exploitation requires at least contributor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.4
NVDPending
|
| Apr 03, 2024 |
CVE-2024-2879
LayerSlider: SQL injection
LayerSlider is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data.
|
See mitigation notes |
CVE9.8
NVD7.5
|
| Nov 22, 2023 |
CVE-2023-47786
Layerslider: Cross-site scripting
Layerslider is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.5
NVD5.4
|
| Nov 22, 2023 |
CVE-2023-47785
Layerslider: Cross-site request forgery
Layerslider is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE7.1
NVD8.8
|
| Apr 25, 2022 |
CVE-2022-1153
LayerSlider: Cross-site scripting
LayerSlider is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE4.8
NVD4.8
|