dbcve.org
PloneApplication

CVE-2017-1000483

MEDIUM · 6.5 CVSS v3.0 Published 2018-01-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Accessing private content via str.format in through-the-web templates and scripts in Plone 2.5-5.1rc1. This improves an earlier hotfix. Since the format method was introduced in Python 2.6, this part of the hotfix is only relevant for Plone 4 and 5.

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

Authenticated users can access private content through the str.format method in Plone's through-the-web templates and scripts. This information disclosure vulnerability affects Plone 4 and 5 (since str.format was introduced in Python 2.6), building upon an earlier incomplete hotfix.

MitigationApply the Plone hotfix for this CVE or upgrade to a patched Plone version (5.1rc1 or later). Verify that TTW templates and scripts no longer expose private content after remediation.

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:= 2.5.5= 3.3= 3.3.1= 3.3.2= 3.3.3= 3.3.4= 3.3.5= 3.3.6= 4.0= 4.0.1= 4.0.2= 4.0.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check Plone version
    Log into the ZMI (Zope Management Interface) at /manage_main or check the version.py file in the Plone installation directory. In the ZMI, navigate to acl_users -> magic.credentials_cookie_auth or check the portal_migration tool for the exact version number.
    Affected if The installed version is between 2.5.5 and 4.3.x, or between 5.0 and 5.1rc1 (all versions that use str.format in TTW contexts before the patch).
  2. Identify TTW templates using str.format
    In the ZMI, navigate to the portal_view_customizations or look for DTML templates and scripts (Python Script objects) in the site root and subfolders. Search for '.format(' within template source code.
    Affected if Any through-the-web templates or Python scripts contain the str.format() method call, especially when accessing object attributes like object/attribute notation.
  3. Inspect script and template permissions
    In the ZMI, check the permissions on identified Python Scripts and Page Templates. Look at the Security tab for each object to see which roles can execute or view the script content.
    Affected if Authenticated users (including low-privilege roles like Member) have permission to execute Python Scripts or view template source code that contain str.format calls accessing private content.
  4. Test for information disclosure
    As an authenticated user with minimal privileges, create a test TTW Python Script using str.format to access restricted content, for example: 'return self.restricted_traverse("portal_properties/site_properties").title.format()'
    Affected if The script executes without Unauthorized error, indicating private content can be accessed through str.format.

If the Plone version is unpatched (4.x before 4.3.17 or 5.x before 5.1rc1) AND TTW templates or scripts using str.format are accessible to authenticated users, the site is vulnerable to this information disclosure.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the Plone hotfix for this CVE or upgrade to a patched Plone version (5.1rc1 or later). Verify that TTW templates and scripts no longer expose private content after remediation.

Fix this in Plone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000483 — 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-2017-1000483 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