# CVE-2012-0901: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via the submit parameter in the YouSayToo WordPress plugin, potentially compromising user sessions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** No
- **Published:** 20 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-27gv-5xfq-qrc6

## What is CVE-2012-0901?

CVE-2012-0901 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Jan 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

Cross-site scripting (XSS) vulnerability in yousaytoo.php in YouSayToo auto-publishing plugin 1.0 for WordPress allows remote attackers to inject arbitrary web script or HTML via the submit parameter.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Attenzione Yousaytoo.

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

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

## Is CVE-2012-0901 being exploited?

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

Public exploit code:

- WordPress Plugin YouSayToo auto-publishing 1.0 - 'submit' Cross-Site Scripting (exploitdb)
- YouSayToo auto-publishing 1.0 - Cross-Site Scripting (nuclei): http/cves/2012/CVE-2012-0901.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0901 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Jan 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-0901 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-2012-0901/ (Markdown: https://insights.sbomify.com/CVE-2012-0901/index.md)
```

## Sources

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

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