CVE-2006-1711
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedPlone 2.0.5, 2.1.2, and 2.5-beta1 does not restrict access to the (1) changeMemberPortrait, (2) deletePersonalPortrait, and (3) testCurrentPassword methods, which allows remote attackers to modify portraits.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePlone versions 2.0.5, 2.1.2, and 2.5-beta1 contain an insecure direct object reference vulnerability where three methods (changeMemberPortrait, deletePersonalPortrait, and testCurrentPortrait) lack proper access control checks, allowing unauthenticated or unauthorized remote attackers to modify member portrait images.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.5= 2.1.2= 2.5_beta1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Plone versionAccess the ZMI (Zope Management Interface) through /manage or check the 'portal_migrations' tool via the Plone setup, or inspect the 'Products/PlonePortal/VERSION' file if accessibleAffected if The installed version matches 2.0.5, 2.1.2, or 2.5-beta1 exactly
-
Verify member portrait feature is enabledCheck if the 'Member' content type is available in the portal by accessing the 'portal_types' tool in the ZMI, or confirm that users can access their personal preferencesAffected if The member portrait functionality is present and users have personal folders or profile access
-
Test unauthenticated access to changeMemberPortrait methodAttempt an HTTP POST request to /manage_changeMemberPortrait or /portal_memberdata/changeMemberPortrait without authentication, checking if the request is accepted without loginAffected if The method accepts requests without requiring authentication or valid authorization credentials
-
Test unauthenticated access to deletePersonalPortrait methodAttempt an HTTP POST request to /manage_deletePersonalPortrait or /portal_memberdata/deletePersonalPortrait without authenticationAffected if The method accepts unauthenticated requests and executes without access control validation
-
Confirm portal_memberdata tool is exposedAccess the 'portal_memberdata' object through the ZMI at /portal_memberdata and inspect whether the changeMemberPortrait, deletePersonalPortrait, and testCurrentPortrait methods existAffected if All three methods are present in portal_memberdata without explicit access restrictions configured
A user is affected if running Plone version 2.0.5, 2.1.2, or 2.5-beta1 with the member portrait feature enabled and the affected methods are accessible without proper authentication checks.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and authorization checks on the affected methods to ensure only authorized users can modify their own portrait images. This typically involves adding role-based access control (RBAC) checks or using Plone's permission system.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2006-1711 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2006-1711 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data