dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-41002

CRITICAL · 9.3 CVSS v4.0 Published 2026-02-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 Infoticketing. This vulnerability allows an unauthenticated attacker to retrieve, create, update, and delete the database by sending a POST request using the 'code' parameter in '/components/cart/cartApplyDiscount.php'.

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 Infoticketing's cartApplyDiscount.php allows unauthenticated attackers to inject malicious SQL queries through the 'code' parameter in POST requests. This critical flaw (CVSS 9.3) enables complete database compromise, including unauthorized retrieval, creation, update, and deletion of data.

MitigationImplement parameterized queries or prepared statements for all database interactions involving user input. Validate and sanitize the 'code' parameter, and apply vendor security patches when available.

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 the vulnerable PHP file
    Search the web root for /components/cart/cartApplyDiscount.php - check if the file exists on the server
    Affected if The file exists and is accessible via web requests
  2. Verify endpoint accepts the code parameter
    Check if the cartApplyDiscount.php script processes a POST parameter named 'code' - review the source code or test sending a request with code=TEST to the endpoint
    Affected if The endpoint accepts and processes a 'code' POST parameter without sanitization
  3. Confirm unauthenticated access
    Test accessing the cartApplyDiscount.php endpoint without providing any authentication tokens or session cookies
    Affected if The endpoint is accessible without any authentication required
  4. Check Infoticketing version
    Identify the installed Infoticketing version - check version files, admin panel, or headers; compare against any known fixed versions from vendor release notes
    Affected if The installed version has not been patched for this SQL injection vulnerability
  5. Inspect input validation
    Review application logs or WAF alerts for SQL injection attempts on the 'code' parameter, or examine if any Web Application Firewall is blocking malicious SQL payloads
    Affected if No WAF or input validation is present to block SQL injection in the 'code' parameter

If the cartApplyDiscount.php endpoint exists, is publicly accessible without authentication, and processes the 'code' POST parameter without proper sanitization or WAF protection, the environment is vulnerable to CVE-2025-41002.

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 or prepared statements for all database interactions involving user input. Validate and sanitize the 'code' parameter, and apply vendor security patches when available.

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-41002 — 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-41002 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