# CVE-2005-2411: Cross-site request forgery in n/a

> Remote attackers can execute commands and perform actions as other users via CSRF in tDiary, requiring user interaction to trigger the malicious URL.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2411, DSA-808-1, GHSA-9mx5-8jqh-gqjm

## What is CVE-2005-2411?

CVE-2005-2411 is a medium-severity vulnerability in n/a, published on 1 Aug 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-Site Request Forgery (CSRF) vulnerability in tDiary 2.1.1, and tDiary 2.0.1 and earlier, allows remote attackers to conduct actions as another user, and execute commands on the server, via a URL that is activated by the user.

## Which versions are affected by CVE-2005-2411?

It affects 1 product.


Products: Tdiary Tdiary.

## How do I fix CVE-2005-2411?

Upgrade to a fixed version.

## Is CVE-2005-2411 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6852](https://insights.sbomify.com/CVE-2006-6852/): Code injection in n/a (medium 6.0)
- [CVE-2010-0726](https://insights.sbomify.com/CVE-2010-0726/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2006-6174](https://insights.sbomify.com/CVE-2006-6174/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2411 and fix it if it is affected.

What it is: CVE-2005-2411 is a medium-severity vulnerability in n/a, published on 1 Aug 2005. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-2411 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-2005-2411/ (Markdown: https://insights.sbomify.com/CVE-2005-2411/index.md)
```

## Sources

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

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