dbcve.org
InjectionWeakness · CWE-74

CVE-2026-6490

HIGH · 7.3 CVSS v3.1 Published 2026-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
A weakness has been identified in QueryMine sms up to 7ab5a9ea196209611134525ffc18de25c57d9593. Impacted is an unknown function of the file admin/deletecourse.php of the component GET Request Parameter Handler. This manipulation of the argument ID causes sql injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The vendor was contacted early about this disclosure but did not respond in any way.

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 · moderate confidence

SQL injection vulnerability in QueryMine sms admin/deletecourse.php via the ID GET parameter. An attacker can manipulate the ID argument to inject malicious SQL queries, potentially allowing unauthorized database access, data exfiltration, or modification. The vulnerability is remotely exploitable and a working exploit is publicly available.

MitigationImmediately restrict access to admin/deletecourse.php to authenticated administrators only; implement parameterized queries or prepared statements for the ID parameter; deploy a WAF as a temporary compensating control until the code is remediated.

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
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 QueryMine sms installation
    Search the web root directory for files or directories containing 'querymine' or 'sms' in the path. Common locations include /var/www/html, /www, or C:\inetpub\wwwroot.
    Affected if QueryMine sms software is present on the server
  2. Verify vulnerable file exists
    Check if the file admin/deletecourse.php exists within the QueryMine sms installation directory.
    Affected if The file admin/deletecourse.php exists in the application hierarchy
  3. Confirm endpoint accessibility
    Attempt to access the URL pattern: http(s)://<host>/admin/deletecourse.php without providing any authentication credentials.
    Affected if The endpoint is accessible without authentication (no login required)
  4. Test ID parameter acceptance
    Send a GET request to admin/deletecourse.php with an ID parameter, such as: admin/deletecourse.php?ID=1
    Affected if The application accepts the ID parameter and processes it without requiring authentication or rejecting the request
  5. Check for SQL injection vulnerability
    Submit malformed SQL syntax in the ID parameter (e.g., ID=1' OR '1'='1 or ID=1 AND 1=1--) and observe if the application returns database errors, unexpected data, or behaves differently than with a normal numeric ID.
    Affected if The ID parameter reflects unsanitized input in SQL queries, causing observable differences in application behavior or database error messages

A user is affected if QueryMine sms is installed, the admin/deletecourse.php file exists, and the ID GET parameter can be accessed without authentication and processes SQL syntax without sanitization.

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

Immediately restrict access to admin/deletecourse.php to authenticated administrators only; implement parameterized queries or prepared statements for the ID parameter; deploy a WAF as a temporary compensating control until the code is remediated.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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