# CVE-2012-0317: Cross-site request forgery in n/a

> Remote attackers can hijack user sessions to modify data via CSRF in Movable Type's commenting or community features.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 3 Mar 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q6pj-7m8h-843g

## What is CVE-2012-0317?

CVE-2012-0317 is a medium-severity vulnerability in n/a, published on 3 Mar 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Movable Type before 4.38, 5.0x before 5.07, and 5.1x before 5.13 allow remote attackers to hijack the authentication of arbitrary users for requests that modify data via the (1) commenting feature or (2) community script.

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

## Which versions are affected by CVE-2012-0317?

It affects 1 product.


Products: Sixapart Movable Type.

## How do I fix CVE-2012-0317?

Upgrade to a fixed version.

## Is CVE-2012-0317 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0752](https://insights.sbomify.com/CVE-2009-0752/): Other in n/a (critical 10.0)
- [CVE-2022-38078](https://insights.sbomify.com/CVE-2022-38078/): Command injection in Movable Type XMLRPC API (critical 9.8)
- [CVE-2021-20837](https://insights.sbomify.com/CVE-2021-20837/): Command injection in Movable Type (critical 9.8)
- [CVE-2016-5742](https://insights.sbomify.com/CVE-2016-5742/): SQL injection in n/a (critical 9.8)
- [CVE-2026-25776](https://insights.sbomify.com/CVE-2026-25776/): Code injection in Movable Type (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0317 and fix it if it is affected.

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

## Sources

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

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