# CVE-2020-37091: Maian Support Helpdesk 4.3 - Cross-Site Request Forgery (Add Admin)

> Attackers can exploit CSRF to create admin accounts and upload PHP files, leading to privilege escalation and remote code execution.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Feb 2026
- **Updated:** 4 Feb 2026
- **Also known as:** GHSA-2rv2-xrc4-x25w

## What is CVE-2020-37091?

CVE-2020-37091 is a medium-severity vulnerability in Maian Support Helpdesk, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Maian Support Helpdesk 4.3 contains a cross-site request forgery vulnerability that allows attackers to create administrative accounts without authentication. Attackers can craft malicious HTML forms to add admin users and upload PHP files with unrestricted file upload capabilities through the FAQ attachment system.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2020-37091?


## How do I fix CVE-2020-37091?

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

## Is CVE-2020-37091 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-37091 and fix it if it is affected.

What it is: CVE-2020-37091 is a medium-severity vulnerability in Maian Support Helpdesk, published on 3 Feb 2026. An attacker can exploit it over the internet without logging in, 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-2020-37091 exists.

Affected product: Maian Support Helpdesk. 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-2020-37091/ (Markdown: https://insights.sbomify.com/CVE-2020-37091/index.md)
```

## Sources

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

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