# CVE-2017-7446: Cross-site request forgery in n/a

> Cross-site request forgery in HelpDEZk allows attackers to obtain admin privileges by tricking authenticated users.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 5 Apr 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7qqw-r4cr-36h5

## What is CVE-2017-7446?

CVE-2017-7446 is a high-severity vulnerability in n/a, published on 5 Apr 2017. 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

HelpDEZk 1.1.1 has CSRF in admin/home#/person/ with an impact of obtaining admin privileges.

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

## Which versions are affected by CVE-2017-7446?

It affects 1 product.


Products: Helpdezk Helpdezk.

## How do I fix CVE-2017-7446?

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

## Is CVE-2017-7446 being exploited?

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

Public exploit code:

- HelpDEZK 1.1.1 - Cross-Site Request Forgery / Code Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2023-3038](https://insights.sbomify.com/CVE-2023-3038/): HelpDezk Community improper authorization (critical 9.8)
- [CVE-2014-8337](https://insights.sbomify.com/CVE-2014-8337/): File upload in n/a (critical 9.8)
- [CVE-2017-14145](https://insights.sbomify.com/CVE-2017-14145/): SQL injection in n/a (critical 9.8)
- [CVE-2017-14146](https://insights.sbomify.com/CVE-2017-14146/): File upload in n/a (high 8.8)
- [CVE-2017-7447](https://insights.sbomify.com/CVE-2017-7447/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-7446 and fix it if it is affected.

What it is: CVE-2017-7446 is a high-severity vulnerability in n/a, published on 5 Apr 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-7446 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-2017-7446/ (Markdown: https://insights.sbomify.com/CVE-2017-7446/index.md)
```

## Sources

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

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