# CVE-2012-2401: Security feature bypass in n/a

> Remote attackers can bypass Same Origin Policy via crafted SWF content in Plupload, requiring user interaction to load malicious content.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **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:** Yes
- **Published:** 21 Apr 2012
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2012-3415, DEBIAN-CVE-2012-2401, GHSA-ch8h-4j2v-gwvg

## What is CVE-2012-2401?

CVE-2012-2401 is a medium-severity vulnerability in Wordpress Wordpress, published on 21 Apr 2012. 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

Plupload before 1.5.4, as used in wp-includes/js/plupload/ in WordPress before 3.3.2 and other products, enables scripting regardless of the domain from which the SWF content was loaded, which allows remote attackers to bypass the Same Origin Policy via crafted content.

Weakness: CWE-264

## Which versions are affected by CVE-2012-2401?

It affects 2 products.


Products: Moxiecode Plupload, Wordpress Wordpress.

## How do I fix CVE-2012-2401?

Upgrade to a fixed version.

## Is CVE-2012-2401 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-2401 and fix it if it is affected.

What it is: CVE-2012-2401 is a medium-severity vulnerability in Wordpress Wordpress, published on 21 Apr 2012. 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-2012-2401 in the wild and no public exploit code.

Affected product: Wordpress Wordpress. 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-2012-2401/ (Markdown: https://insights.sbomify.com/CVE-2012-2401/index.md)
```

## Sources

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

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