# CVE-2013-5937: Cross-site request forgery in n/a

> Remote attackers can trick administrators into deleting database information via CSRF in the Click2Sell Suite module for Drupal.

- **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:** 25 Sep 2013
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2013-4382, GHSA-chr9-m3cf-vvxr

## What is CVE-2013-5937?

CVE-2013-5937 is a medium-severity vulnerability in n/a, published on 25 Sep 2013. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the Click2Sell Suite module 6.x-1.x for Drupal allows remote attackers to hijack the authentication of administrators for requests that delete database information via vectors involving the Drupal Form API.

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

## Which versions are affected by CVE-2013-5937?

It affects 1 product.


Products: Click2sell Click2sell Suite Module.

## How do I fix CVE-2013-5937?

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

## Is CVE-2013-5937 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-5937 and fix it if it is affected.

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

## Sources

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

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