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

> Staff can upload malicious PHP files via avatar modification to execute code and gain server permissions.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Sep 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-9vcv-pqch-f3fm

## What is CVE-2025-56295?

CVE-2025-56295 is a high-severity vulnerability in n/a, published on 16 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

code-projects Computer Laboratory System 1.0 has a file upload vulnerability. Staff can upload malicious files by uploading PHP backdoor files when modifying personal avatar information and use web shell connection tools to obtain server permissions.

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

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

It affects 1 product.


Products: Carmelo Computer Laboratory System.

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

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

## Is CVE-2025-56295 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-60307](https://insights.sbomify.com/CVE-2025-60307/): SQL injection in n/a (critical 9.8)
- [CVE-2025-14641](https://insights.sbomify.com/CVE-2025-14641/): code-projects Computer Laboratory System admin_pic.php unrestricted upload (medium 5.1)
- [CVE-2025-14642](https://insights.sbomify.com/CVE-2025-14642/): code-projects Computer Laboratory System technical_staff_pic.php unrestricted upload (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56295 is a high-severity vulnerability in n/a, published on 16 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56295 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-56295/ (Markdown: https://insights.sbomify.com/CVE-2025-56295/index.md)
```

## Sources

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

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