thirtybees vulnerabilities
Recent CVEs affecting thirtybees products. 3 tracked.
thirtybees has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 2. Most recent: 2023-12-30. Highest priority: CVE-2023-52264 (score 31/100).
- CVE-2023-52264 MEDIUM 6.1 UPGRADE The beesblog (aka Bees Blog) component before 1.6.2 for thirty bees allows Reflected XSS because controllers/f
- CVE-2023-45958 MEDIUM 6.1 DOWNGRADE Thirty Bees Core v1.4.0 was discovered to contain a reflected cross-site scripting (XSS) vulnerability via the
- CVE-2023-45957 MEDIUM 5.4 UPGRADE A stored cross-site scripting (XSS) vulnerability in the component admin/AdminRequestSqlController.php of thir
FAQ
How do I fix thirtybees vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is thirtybees being exploited right now?
None of the tracked thirtybees CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which thirtybees CVE should I patch first?
CVE-2023-52264 currently ranks highest (31/100): The beesblog (aka Bees Blog) component before 1.6.2 for thirty bees allows Reflected XSS because controllers/f.