# CVE-2008-3716: Cross-site request forgery in n/a

> Remote attackers can trick administrators into performing unauthorized save or delete actions, leading to data modification or privilege escalation.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **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:** 19 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-88jr-vwr6-7xqw

## What is CVE-2008-3716?

CVE-2008-3716 is a medium-severity vulnerability in n/a, published on 19 Aug 2008. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Harmoni before 1.6.0 allows remote attackers to make administrative modifications via a (1) save or (2) delete action to an unspecified component.

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

## Which versions are affected by CVE-2008-3716?

It affects 1 product.


Products: Harmoni Harmoni.

## How do I fix CVE-2008-3716?

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

## Is CVE-2008-3716 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3717](https://insights.sbomify.com/CVE-2008-3717/): Harmoni before 1.6.0 does not require administrative privileges to list (1) user names or (2) asset ids, which allows remote attackers to ob (medium 5.0)
- [CVE-2008-3596](https://insights.sbomify.com/CVE-2008-3596/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-3716 and fix it if it is affected.

What it is: CVE-2008-3716 is a medium-severity vulnerability in n/a, published on 19 Aug 2008. 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-2008-3716 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-2008-3716/ (Markdown: https://insights.sbomify.com/CVE-2008-3716/index.md)
```

## Sources

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

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