WordPress security by component
Custom Banners
Plugin description
Custom Banners is a WordPress component with 3 published CVE records in this archive. The latest tracked vulnerability was published Oct 01, 2024; the highest published CVSS base score is 6.1.
Plugin slug:
custom-bannersLatest vulnerability
CVE-2024-8799: Custom Banners: Cross-site scripting
Custom Banners is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
| Safe version |
|
||
|---|---|---|---|
| Oct 01, 2024 |
CVE-2024-8799
Custom Banners: Cross-site scripting
Custom Banners is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE6.1
NVDPending
|
| Jul 12, 2023 |
CVE-2021-4407
Custom Banners: Cross-site request forgery
Custom Banners is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVE4.3
NVDPending
|
| Jul 07, 2014 |
CVE-2014-4724
Custom Banners: Cross-site scripting
Custom Banners 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. The public source does not disclose the vulnerable endpoint, action, parameter or function, so the precise input path remains unknown.
|
See mitigation notes |
CVEPending
NVD4.3
|