# CVE-2014-9344: Cross-site request forgery in n/a

> Remote attackers can hijack administrator sessions to create new admin accounts via CSRF in Snowfox CMS.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8mx3-h42x-23p5

## What is CVE-2014-9344?

CVE-2014-9344 is a medium-severity vulnerability in n/a, published on 8 Dec 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in Snowfox CMS before 1.0.10 allows remote attackers to hijack the authentication of administrators for requests that add a new admin account via a submit action in the admin/accounts/create uri to snowfox/.

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

## Which versions are affected by CVE-2014-9344?

It affects 1 product.


Products: Globiz Solutions Snowfox Content Management System.

## How do I fix CVE-2014-9344?

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

## Is CVE-2014-9344 being exploited?

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

Public exploit code:

- Snowfox CMS 1.0 - Cross-Site Request Forgery (Add Admin) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-9343](https://insights.sbomify.com/CVE-2014-9343/): Open redirect in n/a (medium 5.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-9344 and fix it if it is affected.

What it is: CVE-2014-9344 is a medium-severity vulnerability in n/a, published on 8 Dec 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-9344 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-2014-9344/ (Markdown: https://insights.sbomify.com/CVE-2014-9344/index.md)
```

## Sources

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

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