# CVE-2012-20005: SocialFit WordPress Plugin 1.2.2 Reflected XSS via popup.php msg Parameter


- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-9v64-w835-pg55

## What is CVE-2012-20005?

CVE-2012-20005 is a medium-severity vulnerability in Łukasz Więcek SocialFit, published on 20 Oct 2026. 

### Official description

SocialFit plugin for WordPress through 1.2.2 contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject scripts via the unsanitized msg parameter. Attackers can craft GET requests to /wp-content/plugins/socialfit/popup.php with service=googleplus and malicious msg values to execute script and steal session cookies. Exploitation evidence was first observed by the Shadowserver Foundation on 2023-10-19.

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

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


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

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

## Is CVE-2012-20005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-20005 is a medium-severity vulnerability in Łukasz Więcek SocialFit, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-20005 exists.

Affected product: Łukasz Więcek SocialFit. 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-20005/ (Markdown: https://insights.sbomify.com/CVE-2012-20005/index.md)
```

## Sources

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

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