# CVE-2011-4926: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via the page parameter in the Adminimize WordPress plugin, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** 29 Aug 2012
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mmvc-933r-7cp3

## What is CVE-2011-4926?

CVE-2011-4926 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Aug 2012. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in adminimize/adminimize_page.php in the Adminimize plugin before 1.7.22 for WordPress allows remote attackers to inject arbitrary web script or HTML via the page parameter.

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

## Which versions are affected by CVE-2011-4926?

It affects 1 product.


Products: Bueltge Adminimize.

## How do I fix CVE-2011-4926?

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

## Is CVE-2011-4926 being exploited?

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

Public exploit code:

- WordPress Plugin Adminimize 1.7.21 - 'page' Cross-Site Scripting (exploitdb)
- Adminimize 1.7.22 - Cross-Site Scripting (nuclei): http/cves/2011/CVE-2011-4926.yaml

## Other vulnerabilities in n/a

- [CVE-2011-5128](https://insights.sbomify.com/CVE-2011-5128/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-4926 and fix it if it is affected.

What it is: CVE-2011-4926 is a medium-severity cross-site scripting vulnerability in n/a, published on 29 Aug 2012. 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-2011-4926 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-2011-4926/ (Markdown: https://insights.sbomify.com/CVE-2011-4926/index.md)
```

## Sources

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

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