# CVE-2010-5320: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to modify settings, articles, or credentials via CSRF attacks in MemHT Portal.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **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 Jan 2015
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-vf6w-44qh-j94c

## What is CVE-2010-5320?

CVE-2010-5320 is a medium-severity vulnerability in n/a, published on 3 Jan 2015. 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

Multiple cross-site request forgery (CSRF) vulnerabilities in MemHT Portal 4.0.1 allow remote attackers to hijack the authentication of administrators for requests that (1) modify settings via a configuration action to admin.php, (2) modify articles via an articles action to admin.php, or (3) modify credentials via a users action to admin.php.

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

## Which versions are affected by CVE-2010-5320?

It affects 1 product.


Products: Memht Memht Portal.

## How do I fix CVE-2010-5320?

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

## Is CVE-2010-5320 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-5132](https://insights.sbomify.com/CVE-2008-5132/): SQL injection in n/a (high 7.5)
- [CVE-2008-4457](https://insights.sbomify.com/CVE-2008-4457/): SQL injection in n/a (medium 6.8)
- [CVE-2009-0372](https://insights.sbomify.com/CVE-2009-0372/): File upload in n/a (medium 6.5)
- [CVE-2008-4164](https://insights.sbomify.com/CVE-2008-4164/): Information disclosure in n/a (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-5320 and fix it if it is affected.

What it is: CVE-2010-5320 is a medium-severity vulnerability in n/a, published on 3 Jan 2015. 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-2010-5320 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-2010-5320/ (Markdown: https://insights.sbomify.com/CVE-2010-5320/index.md)
```

## Sources

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

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