dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41008

CRITICAL · 9.3 CVSS v4.0 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 in Sinturno. This vulnerability allows an attacker to retrieve, create, update, and delete databases through the 'client' parameter in the '/_adm/scripts/modalReport_data.php' endpoint.

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

A SQL injection vulnerability exists in the 'client' parameter of the /_adm/scripts/modalReport_data.php endpoint in Sinturno. An unauthenticated attacker can exploit this to inject arbitrary SQL queries, allowing retrieval, creation, update, and deletion of database contents.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements for the client parameter. Apply input validation and ensure database accounts use least privilege. Consider a WAF as a temporary mitigation.

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
None
Authentication
X
User interaction
None
Scope
X

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

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. Locate Sinturno installation
    Search the web server filesystem for Sinturno application files, typically found in web document root directories. Look for directories containing the application name or check known web paths.
    Affected if Sinturno software is present on the system
  2. Verify vulnerable endpoint exists
    Check for the presence of /_adm/scripts/modalReport_data.php within the Sinturno installation directory structure.
    Affected if The file _adm/scripts/modalReport_data.php exists in the application
  3. Check client parameter exposure
    Examine the application's web access logs or test the modalReport_data.php endpoint directly by sending a request with a 'client' parameter to see if the application accepts and processes it.
    Affected if The endpoint accepts and processes a 'client' parameter without authentication
  4. Assess unauthenticated access
    Verify whether the vulnerable endpoint can be accessed without authentication by attempting a request to /_adm/scripts/modalReport_data.php without providing login credentials.
    Affected if The endpoint is accessible without authentication
  5. Confirm SQL handling method
    Review application source code or test for SQL injection by providing SQL meta-characters in the client parameter and observing database behavior or errors.
    Affected if The client parameter appears to concatenate user input directly into SQL queries without parameterized statements

The environment is affected if Sinturno is installed, the vulnerable endpoint exists, and the client parameter can be accessed unauthenticated with direct SQL concatenation.

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

Replace dynamic SQL queries with parameterized queries/prepared statements for the client parameter. Apply input validation and ensure database accounts use least privilege. Consider a WAF as a temporary mitigation.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41008 — 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-2025-41008 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