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

> Remote attackers can hijack administrator sessions to upload or modify files via CSRF in PBBoard.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/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:** 20 Feb 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-rj27-q4wr-4p4v

## What is CVE-2012-1216?

CVE-2012-1216 is a medium-severity vulnerability in n/a, published on 20 Feb 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in admin.php in PBBoard 2.1.4 allow remote attackers to hijack the authentication of administrators for requests that (1) upload a file via an add action or (2) change the contents of a file via a dit action.

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

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

It affects 1 product.


Products: Pbboard Pbboard.

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

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

## Is CVE-2012-1216 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-9215](https://insights.sbomify.com/CVE-2014-9215/): SQL injection in n/a (high 7.5)
- [CVE-2012-4034](https://insights.sbomify.com/CVE-2012-4034/): SQL injection in n/a (high 7.5)
- [CVE-2012-4035](https://insights.sbomify.com/CVE-2012-4035/): Missing authorization in n/a (high 7.5)
- [CVE-2012-4036](https://insights.sbomify.com/CVE-2012-4036/): File upload in n/a (medium 6.8)
- [CVE-2009-3649](https://insights.sbomify.com/CVE-2009-3649/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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