dbcve.org
Qoca AimApplication · Quantatw

CVE-2025-15235

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 Missing Authorization vulnerability, allowing authenticated remote attackers to modify specific network packet parameters, enabling certain system functions to access other users' files.

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

QOCA aim AI Medical Cloud Platform has a missing authorization vulnerability where authenticated remote attackers can modify specific network packet parameters to bypass access controls, enabling unauthorized access to other users' files. This appears to be an Insecure Direct Object Reference (IDOR) or broken access control issue where object-level authorization is not properly validated.

MitigationImplement proper authorization checks to validate that the authenticated user has permission to access the requested file resources. All file access operations should verify user ownership before returning file data.

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 Qoca Aim installation and version
    Locate the Quantatw Qoca Aim application on your system. Check for version information in the application GUI, installation directory, or about dialog. Common locations include the program's main window, help menu, or configuration files in the installation folder.
    Affected if The installed version is lower than 2.7.6 (e.g., 2.7.5, 2.7.0, etc.)
  2. Verify web service or API endpoint exposure
    Determine if the Qoca Aim application exposes a web interface or API service. Check application configuration files, listening network ports (typically 80, 443, or custom ports), or documentation for web service endpoints.
    Affected if The application has an accessible web interface or REST API that handles file operations
  3. Confirm multi-user environment
    Check if the application is configured to support multiple user accounts or if multiple users have access to the system. Review user management settings, authentication configuration, or user database.
    Affected if Multiple user accounts are configured or the system serves multiple authenticated users
  4. Test file access authorization (if environment permits)
    If you have access to multiple test accounts, attempt to access a file owned by one user while authenticated as another user. Modify the request parameters (such as file ID, user ID, or object reference) to see if unauthorized access is possible.
    Affected if A user can access another user's files by manipulating object identifiers in requests

Your environment is affected if Qoca Aim version is below 2.7.6 AND the application exposes file access functionality to multiple authenticated users.

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 proper authorization checks to validate that the authenticated user has permission to access the requested file resources. All file access operations should verify user ownership before returning file data.

Recommended fix Moderate confidence

2.7.6

  1. Identify the currently installed version of Qoca Aim in your environment
  2. Upgrade Qoca Aim to version 2.7.6 or later
  3. After upgrading, verify that the new version is correctly installed
  4. Test that the missing authorization vulnerability is resolved by confirming users can no longer access other users' files through modified network packet parameters

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
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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