dbcve.org
Qoca AimApplication · Quantatw

CVE-2025-15239

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

SQL injection vulnerability in QOCA aim AI Medical Cloud Platform allows authenticated remote attackers to inject arbitrary SQL commands to read database contents. The attack requires authentication, suggesting the injection occurs in a user-controlled input that is not properly sanitized before being used in a database query.

MitigationApply vendor-provided patch or update to a patched version of the platform. Until patched, restrict network access to the platform and monitor for suspicious SQL-like query patterns in logs.

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 product
    Locate the QOCA aim AI Medical Cloud Platform installation and confirm it is Quantatw Qoca Aim. Check product documentation or software inventory for the exact product name and version number.
    Affected if The product is Quantatw Qoca Aim and the version is below 2.7.6
  2. Verify the installed version
    Compare your installed version of Quantatw Qoca Aim against the affected range of versions prior to 2.7.6. Check the application's about page, configuration files, or installation directory for the version string.
    Affected if The installed version is any version prior to 2.7.6
  3. Confirm network accessibility
    Determine if the QOCA aim platform is accessible over the network from untrusted locations. Review firewall rules, network configurations, and access control lists restricting access to the application.
    Affected if The platform is exposed to network access without proper segmentation or access controls
  4. Review authentication configuration
    Check whether authentication is required and properly enforced for accessing the platform. Verify that user accounts exist and login mechanisms are active.
    Affected if The platform allows authenticated access, as the vulnerability requires an authenticated session to exploit the SQL injection

You are affected if you have Quantatw Qoca Aim version prior to 2.7.6 exposed to network users who can authenticate to the platform.

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

Apply vendor-provided patch or update to a patched version of the platform. Until patched, restrict network access to the platform and monitor for suspicious SQL-like query patterns in logs.

Recommended fix High confidence

Upgrade to Qoca Aim version 2.7.6 or later

  1. 1. Identify the current installed version of Qoca Aim by accessing the platform's admin interface or checking system documentation.
  2. 2. Download Qoca Aim version 2.7.6 or later from the official vendor (Quanta Computer) or authorized distribution channel.
  3. 3. Back up the current Qoca Aim installation including all configuration files and database data.
  4. 4. Stop the Qoca Aim service to prevent data corruption during upgrade.
  5. 5. Install version 2.7.6 following the vendor's documented upgrade procedure.
  6. 6. Restart the Qoca Aim service after successful installation.
  7. 7. Verify the installed version is 2.7.6 or later via the admin interface.
  8. 8. Test that the SQL injection vulnerability is remediated by attempting parameterized queries where the vulnerability previously existed.
Caveat Review vendor release notes for any configuration or compatibility changes between your current version and 2.7.6

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

Fix this in Qoca Aim Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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