StudIP · SQL Injection Vulnerability
Source GCVE Database
Not known to be exploited · CVSS 9.1 Critical · fixed in 6.0.3 : patch affected systems as a priority.
Data as of 16 Nov 2026, 20:25 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 6.0.3, 5.4.12
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 17 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CISA SSVC: proof of concept public
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
Timeline
CVE ID reserved
by MITRE Corporation
, 71 days before disclosure
CVE published
on cve.org
, t = 0
CISA SSVC assessment
proof of concept public
, the same day as disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA SSVC, the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.
What to do
AI-suggested
If you cannot patch yet, restrict access to affected StudIP installations and monitor for suspicious activity related to the store() functions.
Description
A critical SQL Injection vulnerability exists in StudIP versions 6.0.x before 6.0.3 and 5.4.x before 5.4.12. This flaw allows a remote attacker to execute arbitrary code and access sensitive information through the store() functions.