dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-2247

HIGH · 8.3 CVSS v4.0 Published 2026-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
89/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
SQL injection vulnerability (SQLi) in Clicldeu SaaS, specifically in the generation of reports, which occurs when a previously authenticated remote attacker executes a malicious payload in the URL generated after downloading the student's report card in the ‘Day-to-day’ section from the mobile application. In the URL of the generated PDF, the session token used does not expire, so it remains valid for days after its generation, and unusual characters can be entered after the ‘id_alu’ parameter, resulting in two types of SQLi: boolean-based blind and time-based blind. Exploiting this vulnerability could allow an attacker to access confidential information in the database.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability exists in the 'id_alu' parameter during report generation in Clicldeu SaaS's Day-to-day mobile application feature. An attacker with valid authentication can inject malicious SQL payloads (boolean-based blind or time-based blind) into the parameter. The issue is compounded by session tokens that never expire, remaining valid for days and allowing prolonged exploitation to extract confidential database information.

MitigationImplement parameterized queries/prepared statements for all database operations involving user input, enforce immediate session token expiration after logout or inactivity, and add input validation to reject special characters in the id_alu parameter.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Clicldeu SaaS deployment
    Inventory your SaaS applications and identify if Clicldeu (or a derivative/white-label version) is in use, particularly the Day-to-day module
    Affected if Clicldeu SaaS with Day-to-day mobile application feature is deployed and accessible
  2. Identify report generation endpoint
    Locate the report generation feature within the Day-to-day mobile application; capture the HTTP request that handles the 'id_alu' parameter during report generation
    Affected if The 'id_alu' parameter is present and accepts user-supplied input in the report generation functionality
  3. Verify authentication requirement
    Confirm that valid authentication (session token) is required to access the vulnerable endpoint; check if the endpoint rejects unauthenticated requests
    Affected if The endpoint requires valid authentication but lacks parameterized query handling for the id_alu parameter
  4. Check session token expiration policy
    Review session management configuration or token validity duration settings; determine if tokens remain active beyond a short timeframe (e.g., days)
    Affected if Session tokens are configured to remain valid for extended periods without automatic expiration
  5. Compare installed version to affected range
    If version information is available for Clicldeu SaaS or its Day-to-day module, compare against any documented affected versions; otherwise treat all versions as potentially affected
    Affected if The deployed version falls within an affected range or version information is unavailable (assume affected)

The environment is affected if Clicldeu SaaS with the Day-to-day mobile application feature is deployed, the report generation endpoint with the id_alu parameter is accessible (even with authentication), and session tokens do not expire promptly.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries/prepared statements for all database operations involving user input, enforce immediate session token expiration after logout or inactivity, and add input validation to reject special characters in the id_alu parameter.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-2247 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-2247 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data