dbcve.org
PloneApplication

CVE-2013-7062

MEDIUM · 6.1 CVSS v3.1 Published 2020-01-02
Fix available
A fix is available. Upgrade to after 4.3.2 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Multiple cross-site scripting (XSS) vulnerabilities in Zope, as used in Plone 3.3.x through 3.3.6, 4.0.x through 4.0.9, 4.1.x through 4.1.6, 4.2.x through 4.2.7, and 4.3 through 4.3.2, allow remote attackers to inject arbitrary web script or HTML via unspecified input in the (1) browser_id_manager or (2) OFS.Image method.

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 confidence

Multiple cross-site scripting (XSS) vulnerabilities in Zope framework allow remote attackers to inject arbitrary web script or HTML via unspecified input in the browser_id_manager or OFS.Image method. The vulnerability affects Plone versions 3.3.x through 3.3.6, 4.0.x through 4.0.9, 4.1.x through 4.1.6, 4.2.x through 4.2.7, and 4.3 through 4.3.2.

MitigationUpgrade to a patched version of Plone (4.3.3 or later for the 4.3 branch, or corresponding patched versions for earlier branches) that addresses the XSS vulnerabilities in Zope's browser_id_manager and OFS.Image components.

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
PloneApplication
Affected:>= 3.3.0, <= 3.3.6>= 4.0.0, <= 4.0.9>= 4.1.0, <= 4.1.6>= 4.2.0, <= 4.2.7>= 4.3.0, <= 4.3.2

CVSS 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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Plone version
    Locate the version file or use the Zope/Plone management interface (ZMI) at /manage to view the product version. Common locations include portal_migration in the Plone control panel or the versions.cfg file in the Plone buildout directory.
    Affected if The installed Plone version falls within 3.3.0-3.3.6, 4.0.0-4.0.9, 4.1.0-4.1.6, 4.2.0-4.2.7, or 4.3.0-4.3.2
  2. Verify browser_id_manager component is accessible
    Access the Zope Management Interface (ZMI) and navigate to the browser_id_manager object in the Zope root or check if the component is loaded in the site configuration. This is typically found under the 'browser_id_manager' id in the Zope object hierarchy.
    Affected if The browser_id_manager component exists and accepts user-supplied input without proper sanitization, allowing XSS injection via unspecified parameters.
  3. Check OFS.Image method exposure
    Inspect the OFS.Image module in the Zope installation to determine if the vulnerable method (typically related to image display or handling) is exposed to web requests. This may involve checking the method permissions and traversal in the ZMI.
    Affected if The OFS.Image method is accessible via web and accepts unsanitized input, permitting script injection.
  4. Confirm web-facing access to vulnerable endpoints
    Determine if the Plone site is exposed to the internet or accessible to untrusted users. Test by accessing typical paths like /manage (ZMI) or observing whether the Plone site allows anonymous or unauthenticated interactions with the affected components.
    Affected if The Plone instance is accessible to remote users who can interact with the browser_id_manager or OFS.Image components without authentication or with low-privilege accounts.

Your environment is affected if you are running any Plone version from 3.3.0 through 3.3.6, 4.0.0 through 4.0.9, 4.1.0 through 4.1.6, 4.2.0 through 4.2.7, or 4.3.0 through 4.3.2, AND the browser_id_manager or OFS.Image components are accessible to users who can inject malicious scripts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.3.2
Interim mitigation

Upgrade to a patched version of Plone (4.3.3 or later for the 4.3 branch, or corresponding patched versions for earlier branches) that addresses the XSS vulnerabilities in Zope's browser_id_manager and OFS.Image components.

Fix this in Plone Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-7062 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-7062 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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