What this page helps you verify fast
This hub clusters tracked records for Custom Banners so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Custom Banners (`custom-banners`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2024-8799, CVE-2021-4407 and CVE-2014-4724, so operators can jump from disclosure to patch validation without scanning the full feed first.
Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.
Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.
Affected range: Versions before 2.1. Fixed version: 2.1.
Affected range: Versions up to 3.3. Fixed version is not listed yet.
Affected range: Versions up to 3.2.2. Fixed version: 3.3.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
| Tracked CVE | Issue Type | Affected Versions | Fixed Version | CVSS |
|---|---|---|---|---|
|
CVE-2014-4724
Custom Banners < 2.1 - Cross-Site Scripting
|
Cross-Site Scripting | Versions before 2.1 | 2.1 | CVSS 7.1 |
|
CVE-2024-8799
Custom Banners <= 3.3 - Reflected Cross-Site Scripting
|
Cross-Site Scripting | Versions up to 3.3 | No patch listed | CVSS 6.1 |
|
CVE-2021-4407
Custom Banners <= 3.2.2 - Cross-Site Request Forgery Bypass
|
Cross-Site Request Forgery | Versions up to 3.2.2 | 3.3 | CVSS 4.3 |
Custom Banners < 2.1 - Cross-Site Scripting
Custom Banners <= 3.3 - Reflected Cross-Site Scripting
Custom Banners <= 3.2.2 - Cross-Site Request Forgery Bypass
This hub clusters tracked records for Custom Banners so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Custom Banners plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and inc...
The Custom Banners plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.2 This is due to missing or incorrect nonce validation on the saveCu...
Cross-site scripting (XSS) vulnerability in the Custom Banners plugin before 2.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the custom_banners_registere...
Sorted by latest disclosure date so newly published issues surface first.
The Custom Banners plugin for WordPress is vulnerable to Reflected Cross-Site Scripting due to the use of add_query_arg without appropriate escaping on the URL in all versions up to, and including, 3.3. This makes it possible for unauthenticated attackers to inject arbitrary web...
The Custom Banners plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.2 This is due to missing or incorrect nonce validation on the saveCustomFields() function. This makes it possible for unauthenticated attackers to save custom...
Cross-site scripting (XSS) vulnerability in the Custom Banners plugin before 2.1 for WordPress allows remote attackers to inject arbitrary web script or HTML via the custom_banners_registered_name parameter to wp-admin/options.php.