PatchTheCVEpbootcms vulnerabilities and fixes
Recent CVEs affecting pbootcms, with upgrade or downgrade steps. 9 tracked.
pbootcms has 9 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 6. Most recent: 2025-12-28. Highest priority: CVE-2025-46109 (score 45/100).
- CVE-2025-15153 LOW 3.7 UPGRADE A weakness has been identified in PbootCMS up to 3.2.12
- CVE-2025-15154 MEDIUM 5.3 UPGRADE A security vulnerability has been detected in PbootCMS up to 3.2.12
- CVE-2025-46109 HIGH 8.8 UPGRADE SQL Injection vulnerability in pbootCMS v.3.2.5 and v.3.2.10 allows a remote attacker to obtain sensitive info
- CVE-2025-3787 LOW 2.7 DOWNGRADE A vulnerability was found in PbootCMS 3.2.5
- CVE-2025-29389 MEDIUM 6.1 DOWNGRADE PbootCMS v3.2.9 contains a XSS vulnerability in admin.php?p=/Content/index/mcode/2#tab=t2.
- CVE-2024-42930 MEDIUM 6.1 DOWNGRADE PbootCMS 3.2.8 is vulnerable to URL Redirect.
- CVE-2024-12793 MEDIUM 4.3 UPGRADE A vulnerability, which was classified as problematic, has been found in PbootCMS up to 5.2.3
- CVE-2024-12789 MEDIUM 6.3 UPGRADE A vulnerability was found in PbootCMS up to 3.2.3
- CVE-2020-19248 MEDIUM 5.1 UPGRADE SQL Injection vulnerability in PbootCMS 1.4.1 in parsing if statements in templates, resulting in a malicious
FAQ
How do I fix pbootcms 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 pbootcms being exploited right now?
None of the tracked pbootcms CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which pbootcms CVE should I patch first?
CVE-2025-46109 currently ranks highest (45/100): SQL Injection vulnerability in pbootCMS v.3.2.5 and v.3.2.10 allows a remote attacker to obtain sensitive info.