The Bug Library Project maintains a focused vulnerability footprint centered on its bug_library product, a niche but more prominent than typical component in its domain. The durable signal reflects application-layer input-handling risks, with observed weaknesses including cross-site scripting in web page generation and unrestricted file upload mechanisms. Current severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Bug Library Project over time
Signals from CVEs in this vendor scope (3 CVEs).
3 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-5450CRITICAL The Bug Library WordPress plugin before 2.1.1 does not check the file type on user-submitted bug reports, allowing an unauthenticated user to upload PHP files | Jul 13, 2024 | 9.1 | 25 | NO | NO |
CVE-2021-38355MEDIUM The Bug Library WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the successimportcount parameter found in the ~/bug-library.php file which allows attackers to | Sep 10, 2021 | 6.1 | 21 | NO | NO |
CVE-2024-5604MEDIUM The Bug Library WordPress plugin before 2.1.2 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site S | Jul 19, 2024 | 5.9 | 18 | NO | NO |
Signals from CVEs in this vendor scope (3 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Bug Library Project.
Media articles that mention a CVE ID that affects a product developed by Bug Library Project — matched by CVE ID, not by vendor name.