Vulnerability in plone-app-users (CVE-2011-1950)
Summary
Vulnerability in plone-app-users (CVE-2011-1950). Data can be tampered with by attackers. Mitigation: upgrade to 1.1.1 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2011-1950 has been found in plone-app-users.
Data can be tampered with by attackers.
What to do: upgrade plone-app-users to 1.1.1 or later.
If unsure, ask your IT team or search "plone-app-users CVE-2011-1950" on the vendor's site.
CVE-2011-1950 (plone-app-users)
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.1.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in plone-app-users.
Check the vendor advisory for the affected versions of plone-app-users.
Severity: ?. Data can be tampered with by attackers.
Update to 1.1.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'plone-app-users' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'plone-app-users' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
plone-app-usersを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade plone-app-users to 1.1.1ステージング環境で 1.1.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- web exchange.xforce.ibmcloud.com
- web github.com
- web plone.org