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

> Remote attackers can hijack user or admin sessions to modify account settings or add pages via CSRF in FlexCMS.

- **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:** No
- **Published:** 18 Sep 2012
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-h9m9-pmjm-hmp3

## What is CVE-2012-1901?

CVE-2012-1901 is a medium-severity vulnerability in n/a, published on 18 Sep 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 FlexCMS 3.2.1 and earlier allow remote attackers to (1) hijack the authentication of users for requests that change account settings via a request to index.php/profile-edit-save or (2) hijack the authentication of administrators for requests that add a new page via a request to admin/pages-new-save.

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

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

It affects 1 product.


Products: Flexcms Flexcms.

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

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

## Is CVE-2012-1901 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1901 exists.

Public exploit code:

- FlexCMS 3.2.1 - Multiple Cross-Site Request Forgery Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-1256](https://insights.sbomify.com/CVE-2009-1256/): SQL injection in n/a (high 7.5)
- [CVE-2009-0534](https://insights.sbomify.com/CVE-2009-0534/): SQL injection in n/a (high 7.5)
- [CVE-2008-3715](https://insights.sbomify.com/CVE-2008-3715/): Cross-site scripting in n/a (low 2.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1901 is a medium-severity vulnerability in n/a, published on 18 Sep 2012. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-1901 exists.

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-1901/ (Markdown: https://insights.sbomify.com/CVE-2012-1901/index.md)
```

## Sources

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

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