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

> Attackers can upload nested ZIP archives containing webshells to achieve remote code execution on E-POINT CMS installations.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 11 Mar 2026
- **Also known as:** GHSA-q346-h3vj-6v27

## What is CVE-2025-65806?

CVE-2025-65806 is a medium-severity vulnerability in n/a, published on 4 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The E-POINT CMS eagle.gsam-1169.1 file upload feature improperly handles nested archive files. An attacker can upload a nested ZIP (a ZIP containing another ZIP) where the inner archive contains an executable file (e.g. webshell.php). When the application extracts the uploaded archives, the executable may be extracted into a web-accessible directory. This can lead to remote code execution (RCE), data disclosure, account compromise, or further system compromise depending on the web server/process privileges. The issue arises from insufficient validation of archive contents and inadequate restrictions on extraction targets.

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

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

It affects 1 product.


Products: E-Point E-Point Cms.

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

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

## Is CVE-2025-65806 being exploited?

There is no known exploitation of CVE-2025-65806 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-65806 is a medium-severity vulnerability in n/a, published on 4 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-65806 in the wild and no public exploit code.

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-65806/ (Markdown: https://insights.sbomify.com/CVE-2025-65806/index.md)
```

## Sources

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

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