CVE-2026-2247
SQL Injection in Clicldeu SaaS Report Generation Exposes Data
Publication date: 2026-02-17
Last updated on: 2026-02-17
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| clickedu | saas_platform | to 2026-01-26 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection (SQLi) issue found in the Clicldeu SaaS platform, specifically in the report generation feature. It occurs when a previously authenticated remote attacker manipulates the URL generated after downloading a student's report card from the mobile application's 'Day-to-day' section.
The URL contains a session token that does not expire for days, and the 'id_alu' parameter in the URL can accept unusual characters. This allows the attacker to perform two types of SQL injection attacks: boolean-based blind and time-based blind SQLi.
By exploiting this vulnerability, the attacker can execute malicious SQL payloads that may lead to unauthorized access to confidential information stored in the database.
How can this vulnerability impact me? :
Exploiting this SQL injection vulnerability can allow an attacker to access confidential information within the database without proper authorization.
Since the session token used in the URL does not expire for days, an attacker can repeatedly exploit this vulnerability over an extended period.
This could lead to data breaches, exposure of sensitive student information, and potential compromise of the integrity and confidentiality of the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know