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

> Remote attackers can hijack administrator sessions to add unauthorized users via CSRF, requiring admin interaction.

- **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:** 13 Jan 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cvjm-jx7m-3jqc

## What is CVE-2014-10008?

CVE-2014-10008 is a medium-severity vulnerability in n/a, published on 13 Jan 2015. 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

Multiple cross-site request forgery (CSRF) vulnerabilities in Stark CRM 1.0 allow remote attackers to hijack the authentication of administrators for requests that add (1) an administrator via a crafted request to the admin page, (2) an agent via a crafted request to the agent page, (3) a sub-agent via a crafted request to the sub_agent page, (4) a partner via a crafted request to the partner page, or (5) a client via a crafted request to the client page.

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

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

It affects 1 product.


Products: Iwcn Stark Crm.

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

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

## Is CVE-2014-10008 being exploited?

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

Public exploit code:

- Stark CRM 1.0 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-10009](https://insights.sbomify.com/CVE-2014-10009/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-10008 is a medium-severity vulnerability in n/a, published on 13 Jan 2015. 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-10008 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-10008/ (Markdown: https://insights.sbomify.com/CVE-2014-10008/index.md)
```

## Sources

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

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