CVE-2025-12465: OpenSolution QuickCMS · SQL Injection
Affects OpenSolution QuickCMSSource CVE Database V5
Not known to be exploited · CVSS 8.6 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 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 |
|---|---|---|
| OpenSolution QuickCMS | Affected
| Fixed in– |
AI-suggested
- Immediately audit and restrict access to high-privileged accounts that can invoke the aFilesDelete function, enforcing the principle of least privilege.
- Implement rigorous input validation and sanitization on all user inputs, especially those interacting with SQL queries, to neutralize special characters and prevent injection.
- Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious SQL injection patterns targeting QuickCMS endpoints.
- Monitor database logs and application behavior for anomalies indicative of blind SQL injection attempts, such as unusual query patterns or timing discrepancies.
- Isolate QuickCMS instances in segmented network zones to limit lateral movement if compromise occurs.
- Engage with OpenSolution for updates or patches and plan for rapid deployment once available.
- Consider upgrading or migrating to alternative CMS platforms with active security support if patching is delayed.
- Conduct regular security assessments and penetration testing focusing on injection vulnerabilities.
- Educate administrators and developers on secure coding practices and the risks of SQL injection.
- Backup CMS databases frequently and verify restoration procedures to minimize impact of potential data corruption or deletion.
Description
A Blind SQL injection vulnerability has been identified in QuickCMS. Improper neutralization of input provided by a high-privileged user into aFilesDelete allows for Blind SQL Injection attacks. The vendor was notified early about this vulnerability, but didn't respond with the details of vulnerability or vulnerable version range. Only version 6.8 was tested and confirmed as vulnerable, other versions were not tested and might also be vulnerable.