EUVD-2026-50310
GHSA-cjf9-hgp6-3h22
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
PR:H because admin authentication is mandatory; C:N because vendor confirms no data exfiltration pathway; I:L and A:L for validation bypass and database destruction risk.
Primary rating from Vendor (cert).
CVSS VectorVendor: cert
Lifecycle Timeline
1DescriptionCVE.org
A Blind SQL injection vulnerability has been identified in Quick.CMS. Improper neutralization of input provided by a high-privileged user into multiple fields in administration panel allows for Blind SQL Injection attacks.
The vendor states that this administration panel already allows for significant modification capabilities. The SQL injection vulnerability primarily enables bypassing front-end validation controls and potential database destruction. Given the trust model in which this application is designed to be administered, remediation of this issue was not deemed necessary by the vendor.
This vulnerability has been found in version 6.8, but other versions might also be vulnerable.
AnalysisAI
Blind SQL injection in Quick.CMS 6.8 is exploitable by a high-privileged administrator through multiple fields in the administration panel, bypassing front-end validation controls and enabling potential database destruction. The vendor has explicitly declined to patch this issue, citing the administration panel's existing broad modification capabilities as context that limits the incremental risk. No public exploit code or CISA KEV listing exists at time of analysis, and the CVSS 4.0 score of 5.1 reflects the high-privilege prerequisite that significantly constrains real-world impact.
Technical ContextAI
Quick.CMS is a commercial CMS product developed by OpenSolution (opensolution.org). CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) describes the root cause: user-supplied input to administration panel fields is not properly sanitized before being incorporated into SQL queries, enabling blind SQL injection - a technique where an attacker infers database content or structure through observable side effects (e.g., conditional true/false responses, timing differences) rather than direct data exfiltration. The CVSS 4.0 vector AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N indicates the affected application is network-accessible and requires high privileges, with impact limited to low integrity and availability - consistent with the vendor's statement that the injection primarily enables bypassing front-end validation and potential database destruction rather than data exfiltration. The vulnerability was confirmed in version 6.8; other versions are not ruled out.
RemediationAI
No vendor-released patch identified at time of analysis - the vendor has explicitly stated remediation is not deemed necessary given the application's trust model. Because no official fix exists, compensating controls are the only mitigation path. Restrict administrative panel access to internal networks or VPN only, reducing exposure to the network attack vector (AV:N) and limiting exploitation to actors already inside the trusted network. Implement strong, unique credentials and multi-factor authentication for all administrator accounts to reduce the risk of credential compromise that would enable exploitation. Enable database activity monitoring or query logging to detect anomalous SQL patterns. Consider evaluating alternative CMS platforms if database integrity guarantees are a firm security requirement. Each of these controls carries trade-offs: VPN/network restriction adds operational friction for remote administration; MFA is effective but does not eliminate insider risk. Organizations should formally accept, transfer, or mitigate this risk given the vendor's stance.
Same weakness CWE-89 – SQL Injection
View allShare
External POC / Exploit Code
Leaving vuln.today