dbcve.org
Qoca AimApplication · Quantatw

CVE-2025-15238

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-05
Fix available
A fix is available. Upgrade to 2.7.6 or later.
See remediation →
71/100
Remediation priority · Elevated
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
QOCA aim AI Medical Cloud Platform developed by Quanta Computer has a SQL Injection vulnerability, allowing authenticated remote attackers to inject arbitrary SQL commands to read database contents.

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

The QOCA aim AI Medical Cloud Platform contains a SQL Injection vulnerability that allows authenticated remote attackers to inject arbitrary SQL commands. Since the attacker needs authentication, this suggests the application fails to properly sanitize SQL queries when handling user input within the authenticated context, enabling database content enumeration.

MitigationImplement parameterized queries (prepared statements) for all database interactions and apply strict input validation on user-supplied data within the authenticated areas of the application. Conduct a comprehensive code review to identify and remediate other potential injection points.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Qoca AimApplication
Affected:< 2.7.6

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

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

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 the installed Qoca Aim version
    Access the application web interface and look for version information in the login page, footer, or About/Help section. Alternatively, check the application's configuration files (such as config.php, app.properties, or version.xml in the installation directory) for a version field.
    Affected if The displayed or configured version number is lower than 2.7.6 (for example, 2.7.5, 2.7.0, or any version starting with 2.x where x < 7, or any version 1.x).
  2. Verify the web application is accessible
    Confirm that the Qoca Aim web portal is reachable by attempting to access its URL (typically https://server/qoca or similar). Check if the login page loads successfully.
    Affected if The web interface is accessible over the network and accepts authentication requests.
  3. Confirm authentication is enabled and functional
    Log into the Qoca Aim portal using valid credentials. Observe whether the application accepts user input in authenticated areas such as search fields, patient records, or reporting modules.
    Affected if Authentication is required and functional, allowing access to user-authenticated sections of the application.
  4. Inspect database interaction modules
    Within the authenticated interface, navigate to features that accept user input for database queries, such as search functions, report generators, or data export tools. Check the application's configuration for direct SQL execution settings or debug modes.
    Affected if User-supplied input in authenticated areas is processed through direct SQL queries without visible use of parameterized queries.

If the installed Qoca Aim version is below 2.7.6 and the web application is accessible with authentication enabled, the environment is likely affected by this SQL Injection vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 2.7.6 or later
Fixed in 2.7.6
Interim mitigation

Implement parameterized queries (prepared statements) for all database interactions and apply strict input validation on user-supplied data within the authenticated areas of the application. Conduct a comprehensive code review to identify and remediate other potential injection points.

Recommended fix Moderate confidence

2.7.6

  1. Obtain QOCA aim version 2.7.6 or later from the official Quanta Computer vendor channels
  2. Backup the current QOCA aim installation and database before upgrading
  3. Install QOCA aim version 2.7.6 or latest stable release
  4. Verify the SQL injection vulnerability is resolved by testing the previously vulnerable endpoint
  5. Confirm normal application functionality after the upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Qoca Aim Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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