CVE-2011-4030

CVE-2011-4030 is a high-severity security vulnerability in Plone (pip), affecting versions >= 4.0, <= 4.0.9. It is fixed in 4.0.10, 4.1.1, 4.2a3.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Plone anonymous access to sub-objects in CMFEditions where KwAsAttributes classes were publishable

The CMFEditions component 2.x in Plone 4.0.x through 4.0.9, 4.1, and 4.2 through 4.2a2 does not prevent the KwAsAttributes classes from being publishable, which allows remote attackers to access sub-objects via unspecified vectors, a different vulnerability than CVE-2011-3587.

Impact

Affected versions

Plone (>= 4.0, <= 4.0.9) Plone (>= 4.1, < 4.1.1) Plone (>= 4.2a1, <= 4.2a2)

Security releases

Plone → 4.0.10 (pip) Plone → 4.1.1 (pip) Plone → 4.2a3 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environmentNew to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Plone to 4.0.10 or later; Plone to 4.1.1 or later; Plone to 4.2a3 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2011-4030? CVE-2011-4030 is a high-severity security vulnerability in Plone (pip), affecting versions >= 4.0, <= 4.0.9. It is fixed in 4.0.10, 4.1.1, 4.2a3.
  2. Which versions of Plone are affected by CVE-2011-4030? Plone (pip) versions >= 4.0, <= 4.0.9 is affected.
  3. Is there a fix for CVE-2011-4030? Yes. CVE-2011-4030 is fixed in 4.0.10, 4.1.1, 4.2a3. Upgrade to this version or later.
  4. Is CVE-2011-4030 exploitable, and should I be worried? Whether CVE-2011-4030 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2011-4030 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2011-4030?
    • Upgrade Plone to 4.0.10 or later
    • Upgrade Plone to 4.1.1 or later
    • Upgrade Plone to 4.2a3 or later

Other vulnerabilities in Plone

Stop the waste.
Protect your environment with Kodem.