# CVE-2021-36719: Cybonet - PineApp

> Authenticated attackers can upload malicious files via nicUpload.php to execute remote code on the server.

- **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:** 8 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hvhx-qhmq-cpjp

## What is CVE-2021-36719?

CVE-2021-36719 is a high-severity vulnerability in Cybonet PineApp - Mail Secure, published on 8 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

PineApp - Mail Secure - The attacker must be logged in as a user to the Pineapp system. The attacker exploits the vulnerable nicUpload.php file to upload a malicious file,Thus taking over the server and running remote code.

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

## Which versions are affected by CVE-2021-36719?

It affects 1 product.


Products: Cybonet Mail Secure.

## How do I fix CVE-2021-36719?

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

## Is CVE-2021-36719 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-36719 and fix it if it is affected.

What it is: CVE-2021-36719 is a high-severity vulnerability in Cybonet PineApp - Mail Secure, published on 8 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-36719 in the wild and no public exploit code.

Affected product: Cybonet PineApp - Mail Secure. 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-2021-36719/ (Markdown: https://insights.sbomify.com/CVE-2021-36719/index.md)
```

## Sources

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

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