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

> A CSRF vulnerability in the JW Player WordPress plugin allows attackers to trick administrators into deleting players, 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:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Jun 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-67ph-qxrg-rr9v

## What is CVE-2014-4030?

CVE-2014-4030 is a medium-severity vulnerability in n/a, published on 25 Jun 2014. 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 JW Player plugin before 2.1.4 for WordPress allows remote attackers to hijack the authentication of administrators for requests that remove players via a delete action to wp-admin/admin.php.

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

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

It affects 1 product.


Products: Longtailvideo Jw Player for Flash \& Html5 Video Plugin.

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

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

## Is CVE-2014-4030 being exploited?

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

Public exploit code:

- WordPress Plugin JW Player for Flash & HTML5 Video - Cross-Site Request Forgery (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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