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

> A CSRF vulnerability in the Blue Wrench Video Widget plugin allows attackers to hijack administrator sessions and embed malicious JavaScript URLs.

- **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:** 15 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-mw8f-qp6v-5695

## What is CVE-2013-6797?

CVE-2013-6797 is a medium-severity vulnerability in n/a, published on 15 Nov 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 bluewrench-video-widget.php in the Blue Wrench Video Widget plugin before 2.0.0 for WordPress allows remote attackers to hijack the authentication of administrators for requests that embed arbitrary URLs via the bw_url parameter in the bw-videos page to wp-admin/admin.php, as demonstrated by embedding a URL to a JavaScript file.

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

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

It affects 1 product.


Products: Sunil Nanda Blue Wrench Video Widget.

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

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

## Is CVE-2013-6797 being exploited?

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

Public exploit code:

- WordPress Plugin Blue Wrench Video Widget - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-6797 is a medium-severity vulnerability in n/a, published on 15 Nov 2013. An attacker needs administrator access to exploit it, 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-2013-6797 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-2013-6797/ (Markdown: https://insights.sbomify.com/CVE-2013-6797/index.md)
```

## Sources

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

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