WordPress Banner System plugin <= 1.0.0 - Broken Access Control vulnerability

published 2024-12-16 last yr. modified 2026-06-17 4mo ago also EUVD-2024-52482

cvss: 8.2; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

Missing Authorization vulnerability in Saul Morales Pacheco Banner System banner-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Banner System: from n/a through <= 1.0.0.

Is CVE-2024-54359 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: last yr. (2024-12-16)

Exploit prediction

0.69% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by	version	score	vector
CNA	3.1	8.2	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L

Affected products

Saul Morales Pacheco Banner System

Classification

Weakness

CWE-862 Missing Authorization

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/Wordpress/Plugin/banner-system/vulnerability/wordpress-banner-system-plugin-1-0-0-broken-access-cont
vdb-entry

Sources

CVE List CVE-2024-54359
NVD CVE-2024-54359

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.