CongaApplication · Redhat
CVE-2011-0720
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 · uneditedUnspecified vulnerability in Plone 2.5 through 4.0, as used in Conga, luci, and possibly other products, allows remote attackers to obtain administrative access, read or create arbitrary content, and change the site skin via unknown vectors.
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 · moderate confidencePlone CMS versions 2.5 through 4.0 contain an unspecified vulnerability allowing remote unauthenticated attackers to gain administrative access, read/create arbitrary content, and modify site appearance. The vulnerability also affects Conga and luci products that use affected Plone versions.
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
CongaApplication
all versions
LuciApplication
all versions= 2.5= 2.5.1= 2.5.2= 2.5.3= 2.5.4= 2.5.5= 3.0= 3.0.1= 3.0.2= 3.0.3= 3.0.4= 3.0.5CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 Plone installation and versionLocate the Plone installation directory and check the version.py or version.txt file. Common paths include /opt/plone or /var/plone. Run 'python -c "import Plone; print(Plone.__version__)"' if Plone is importable, or check the 'Products.CMFPlone' egg version.Affected if The installed Plone version is 2.5, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.5, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.0.4, or 3.0.5, or falls within the 2.5-4.0 range.
-
Check for Conga package presenceQuery the system package manager for installed Conga packages. On RPM-based systems run 'rpm -qa | grep -i conga'. On Debian-based systems run 'dpkg -l | grep -i conga'.Affected if Any version of Redhat Conga is installed.
-
Check for Luci package presenceQuery the system package manager for installed Luci packages. On RPM-based systems run 'rpm -qa | grep -i luci'. On Debian-based systems run 'dpkg -l | grep -i luci'.Affected if Any version of Redhat Luci is installed.
-
Verify Plone admin interface exposureCheck network listeners on common Plone ports (8080, 8443, 80, 443). Run 'netstat -tlnp' or 'ss -tlnp' and look for Plone-serving processes. Review firewall rules and reverse proxy configurations that may expose the Zope/Plone management interface.Affected if The Plone administrative interface is reachable from untrusted networks without network access restrictions.
A system is affected if Plone version is any release from 2.5 through 3.0.5, or if either the Conga or Luci packages are installed, particularly when the admin interface is network-exposed.
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 dataUpgrade to a supported Plone version (4.1 or later for Plone 4 series, or preferably the latest stable release). For systems unable to upgrade immediately, restrict network access to Plone administrative interfaces and ensure Plone is not directly exposed to untrusted networks.
Fix this in Conga
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0720 — 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-2011-0720 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