CVE-2025-46109: PbootCMS · SQL Injection
Affects PbootCMSSource CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 36% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubpbootcmspro/PbootCMSpkg:github/pbootcmspro/PbootCMSOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Immediate assessment of all pbootCMS installations to identify versions 3.2.5 and 3.2.10 in use.
- Apply any available patches or updates from the pbootCMS vendor as soon as they are released. In the absence of official patches, implement web application firewall (WAF) rules to detect and block suspicious SQL injection patterns in GET requests targeting pbootCMS endpoints.
- Employ input validation and parameterized queries or prepared statements in custom code interfacing with pbootCMS databases to prevent injection.
- Conduct thorough security audits and penetration testing focused on injection vulnerabilities in all web applications.
- Monitor web server logs for unusual or malformed GET requests that could indicate exploitation attempts.
- Restrict database user privileges to the minimum necessary to limit the impact of potential injection attacks.
- Educate development and IT teams about secure coding practices and the risks associated with SQL injection.
- Consider deploying runtime application self-protection (RASP) tools to detect and block injection attacks in real-time. These measures, combined, provide layered defense beyond generic patching advice and help mitigate the risk until official fixes are available.
Description
SQL Injection vulnerability in pbootCMS v.3.2.5 and v.3.2.10 allows a remote attacker to obtain sensitive information via a crafted GET request