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

> Authenticated users can trigger XSS and potential code execution via unvalidated profile images in the Janrain Engage Drupal module.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hhwf-x424-rgm4

## What is CVE-2011-0771?

CVE-2011-0771 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Janrain Engage (formerly RPX) module 6.x-1.3 for Drupal does not validate the file for a profile image, which allows remote authenticated users to conduct cross-site scripting (XSS) attacks and possibly execute arbitrary PHP code by causing a crafted avatar to be downloaded from an external login provider site.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Janrain Rpx.

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

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

## Is CVE-2011-0771 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-2296](https://insights.sbomify.com/CVE-2012-2296/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0771 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Feb 2011. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0771 in the wild and no public exploit code.

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-0771/ (Markdown: https://insights.sbomify.com/CVE-2011-0771/index.md)
```

## Sources

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

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