# CVE-2025-63748: File upload in n/a

> Authenticated users can upload and execute arbitrary PHP files via the attachment feature, leading to remote code execution.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-w28j-c2qx-49r3

## What is CVE-2025-63748?

CVE-2025-63748 is a high-severity vulnerability in n/a, published on 17 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

QaTraq 6.9.2 allows authenticated users to upload arbitrary files via the "Add Attachment" feature in the "Test Script" module. The application fails to restrict file types, enabling the upload of executable PHP files. Once uploaded, the file can be accessed through the "View Attachment" option, which executes the PHP payload on the server.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

## Which versions are affected by CVE-2025-63748?

It affects 1 product.


Products: Testmanagement Qatraq.

## How do I fix CVE-2025-63748?

No fix has been published for CVE-2025-63748 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-63748 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63748 exists.

## Other vulnerabilities in n/a

- [CVE-2025-63747](https://insights.sbomify.com/CVE-2025-63747/): Hardcoded credentials in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63748 and fix it if it is affected.

What it is: CVE-2025-63748 is a high-severity vulnerability in n/a, published on 17 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63748 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-63748/ (Markdown: https://insights.sbomify.com/CVE-2025-63748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-63748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-63748
- OSV: https://osv.dev/vulnerability/CVE-2025-63748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-63748/
Summaries are generated and may contain mistakes; the official description above is the record.