CVE-2026-51346: SQL Injection vulnerability in StudIP 6.0.x before 6.0.3 and 5.4.x before 5.4.12 allows a remote attacker t...
SQL Injection vulnerability in StudIP 6.0.x before 6.0.3 and 5.4.x before 5.4.12 allows a remote attacker to execute arbitrary code and obtain sensitive information via the store() functions.
Security readout for executives and security teams
Plain-English summary
Stud.IP installations running 6.0.x before 6.0.3 or 5.4.x before 5.4.12 may let an unauthenticated remote attacker manipulate database queries. The supplied CVE states this could expose sensitive information and enable arbitrary code execution, creating a serious risk to institutional data and systems.
Executive priority
Treat as an urgent remediation item for every affected, network-reachable Stud.IP deployment. Prioritize internet-facing and sensitive-data environments, assign an owner, and require version confirmation after upgrading. Investigate suspicious activity, but do not claim compromise solely from exposure.
Technical view
CVE-2026-51346 is a CWE-89 SQL injection in Stud.IP store() functions. CVSS 3.1 scores it 9.1 critical: network-accessible, low complexity, no privileges, and no user interaction, with high confidentiality and integrity impact. The supplied material does not identify the precise vulnerable endpoints or parameters.
Likely exposure
Highest exposure exists where affected Stud.IP versions are reachable from untrusted networks. The CVSS vector indicates authentication is not required. The bundle does not provide reliable affected CPEs, deployment prevalence, or configuration prerequisites, so organizations must confirm installed versions directly.
Exploitation context
The supplied sources do not establish active exploitation, and this CVE is not identified as being in KEV. However, its unauthenticated network attack path, low stated complexity, and potential for sensitive-data access or code execution make rapid remediation prudent.
Researcher notes
The record attributes SQL injection to unspecified store() functions but does not identify endpoints, inputs, root cause details, or technical patch changes. Structured affected-product data is unavailable in the bundle. Avoid extrapolating beyond the explicitly named Stud.IP branches and versions.
Mitigation direction
Upgrade Stud.IP 6.0.x installations to 6.0.3 or later.
Upgrade Stud.IP 5.4.x installations to 5.4.12 or later.
Check Stud.IP vendor guidance for any branch-specific instructions or additional mitigations.
Restrict untrusted network access until remediation is completed where immediate upgrading is impossible.
Review database and application logs for suspicious requests affecting store-related functionality.
Validation and detection
Inventory all Stud.IP deployments and record their exact versions.
Confirm no installation remains below 6.0.3 on the 6.0 branch.
Confirm no installation remains below 5.4.12 on the 5.4 branch.
Verify upgrades using application version information and deployment records.
Review relevant logs for anomalous database errors, unexpected queries, or sensitive-data access.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-89: Database access and collection lookup
Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-89 · source CWE mapping
Improper Neutralization of Special Elements used in an SQL Command
Improper Neutralization of Special Elements used in an SQL Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.