dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41019

CRITICAL · 9.3 CVSS v4.0 Published 2025-10-16
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 in Sergestec's SISTICK v7.2. This vulnerability allows an attacker to retrieve, create, update, and delete databases through the 'id' parameter in '/index.php?view=ticket_detail'.

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 in Sergestec SISTICK v7.2 allows remote attackers to execute arbitrary SQL commands via the 'id' parameter in the /index.php?view=ticket_detail endpoint. This enables full database compromise including read, write, update, and delete operations.

MitigationApply vendor-supplied patch for SISTICK v7.2 immediately. If no patch is available, temporarily disable the ticket_detail endpoint or deploy WAF rules to block SQL injection attempts until a fix can be implemented.

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. Identify if SISTICK is installed
    Check for the presence of Sergestec SISTICK application by inspecting web server directories or scanning for SISTICK-specific files and paths
    Affected if The application is installed and accessible on the target system
  2. Determine SISTICK version
    Locate version information in the application (check application configuration files, footer, about page, or version metadata files) and compare to v7.2
    Affected if The installed version is SISTICK v7.2 or if version cannot be determined but the application matches the affected product
  3. Verify ticket_detail endpoint exists
    Attempt to access or probe /index.php?view=ticket_detail on the web server
    Affected if The endpoint responds and is accessible without authentication restrictions
  4. Confirm id parameter acceptance
    Send a request to the ticket_detail endpoint with an id parameter (e.g., ?id=1) and observe if it is processed
    Affected if The id parameter is accepted and used in database queries without apparent sanitization
  5. Check for input validation or WAF protection
    Inspect application configuration files, web server settings, or WAF logs for SQL injection protection mechanisms on the ticket_detail endpoint
    Affected if No input validation, parameterized queries, or WAF rules are detected protecting the id parameter

The environment is affected if SISTICK v7.2 is running and the ticket_detail endpoint with the id parameter is accessible without proper SQL injection protection.

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

Apply vendor-supplied patch for SISTICK v7.2 immediately. If no patch is available, temporarily disable the ticket_detail endpoint or deploy WAF rules to block SQL injection attempts until a fix can be implemented.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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