# CVE-2011-1950: Plone and plone.app.users allow remote authenticated users to modify the properties of arbitrary accounts

> Authenticated users can modify arbitrary account properties in Plone, potentially leading to privilege escalation or data tampering.

- **Severity:** Medium 5.5 (`AV:N/AC:L/Au:S/C:N/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:** Yes
- **Published:** 6 Jun 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2qx8-589j-gcpx, PYSEC-2011-16, PYSEC-2026-2888

## What is CVE-2011-1950?

CVE-2011-1950 is a medium-severity missing authorization vulnerability in Plone Plone, published on 6 Jun 2011. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

plone.app.users in Plone 4.0 and 4.1 allows remote authenticated users to modify the properties of arbitrary accounts via unspecified vectors, as exploited in the wild in June 2011.

Weakness: CWE-264

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

10 open source packages ship an affected version, including plone, Plone and plone-app-users. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `plone` | PyPI | All versions | 4.1.1 |
| `plone` | PyPI | From 4.0.1 | 4.0.6 |
| `plone` | PyPI | From 4.1.0 | 4.1.1 |
| `Plone` | PyPI | From 4.0.1 | 4.0.6 |
| `Plone` | PyPI | From 4.1.0 | 4.1.1 |
| `plone-app-users` | PyPI | From 1.0a1 | 1.0.5, 1.1.1 |
| `plone-app-users` | PyPI | From 1.0a1 | 1.0.5 |
| `plone-app-users` | PyPI | From 1.1b1 | 1.1.1 |
| `plone.app.users` | PyPI | From 1.0a1 | 1.0.5 |
| `plone.app.users` | PyPI | From 1.1b1 | 1.1.1 |

Products: Plone Plone.

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

Upgrade plone to a fixed version for your release line: 4.1.1 or 4.0.6.

## Is CVE-2011-1950 being exploited?

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

## Other vulnerabilities in Plone Plone

- [CVE-2021-33509](https://insights.sbomify.com/CVE-2021-33509/): Incorrect Permission Assignment for Critical Resource in Plone (critical 9.9)
- [CVE-2020-35190](https://insights.sbomify.com/CVE-2020-35190/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-7941](https://insights.sbomify.com/CVE-2020-7941/): Plone Unauthenticated Write Vulnerability (critical 9.8)
- [CVE-2011-3587](https://insights.sbomify.com/CVE-2011-3587/): Zope Command Execution Vulnerability (critical 9.3)
- [CVE-2021-33926](https://insights.sbomify.com/CVE-2021-33926/): Server-Side Request Forgery in Plone CMS (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1950 is a medium-severity missing authorization vulnerability in Plone Plone, published on 6 Jun 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-1950 in the wild and no public exploit code.

Affected packages and fixed versions:
- plone (PyPI): affected all versions; fixed in 4.1.1
- plone (PyPI): affected from 4.0.1; fixed in 4.0.6
- plone (PyPI): affected from 4.1.0; fixed in 4.1.1
- Plone (PyPI): affected from 4.0.1; fixed in 4.0.6
- Plone (PyPI): affected from 4.1.0; fixed in 4.1.1
- plone-app-users (PyPI): affected from 1.0a1; fixed in 1.0.5, 1.1.1
- plone-app-users (PyPI): affected from 1.0a1; fixed in 1.0.5
- plone-app-users (PyPI): affected from 1.1b1; fixed in 1.1.1
- plone.app.users (PyPI): affected from 1.0a1; fixed in 1.0.5
- plone.app.users (PyPI): affected from 1.1b1; fixed in 1.1.1

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

## Sources

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

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