WordPress security by component
Announcement & Notification Banner – Bulletin
Plugin description
Announcement & Notification Banner – Bulletin is a WordPress component with 4 published CVE records in this archive. The latest tracked vulnerability was published Nov 21, 2024; the highest CVE/CNA score is 7.6.
Plugin slug:
bulletin-announcementsLatest vulnerability
CVE-2024-10682: Announcement & Notification Banner – Bulletin: Cross-site scripting
Announcement & Notification Banner – Bulletin 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.
| Safe version |
|
||
|---|---|---|---|
| Nov 21, 2024 |
CVE-2024-10682
Announcement & Notification Banner – Bulletin: Cross-site scripting
Announcement & Notification Banner – Bulletin 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.
|
See mitigation notes |
CVE6.1
NVDPending
|
| Mar 29, 2024 |
CVE-2024-30478
WordPress Announcement & Notification Banner Plugin – Bulletin: SQL injection
WordPress Announcement & Notification Banner Plugin – Bulletin is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
|
See mitigation notes |
CVE7.6
NVD7.2
|
| Jun 09, 2023 |
CVE-2023-2067
Announcement & Notification Banner – Bulletin: Cross-site request forgery
Announcement & Notification Banner – Bulletin 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.
|
See mitigation notes |
CVE6.3
NVD5.4
|
| Jun 09, 2023 |
CVE-2023-2066
Announcement & Notification Banner – Bulletin: A security weakness
Announcement & Notification Banner – Bulletin is affected by a security weakness. Exploitation requires at least subscriber-level access. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE6.3
NVD4.3
|