Plone 5.2.14 released

Release notes for Plone 5.2.14

If you want to jump straight in, here are two important links:


Major changes since 5.2.13:

  • This includes security fixes from today's announcement:
  • Zope:
    • Security fixes in AccessControl and RestrictedPython. See community announcement.
    • Allow only some image types to be displayed inline. Force download for others, especially SVG images.
    • Tighten down the ZMI frame source logic to only allow site-local sources.
  • plone.namedfile: Fix stored XSS (Cross Site Scripting) for SVG images.
  • When ++api++ is in the url multiple times, redirect to the proper url.
  • plone.restapi:
    • Fix stored XSS (Cross Site Scripting) for SVG image in user portrait.
  • Products.CMFCore: Make decodeFolderFilter and encodeFolderFilter non-public.
    This is the workaround from CVE-2023-36814.
    • Fix various problems when using the Indonesian language in a multilingual setup.
      This language has id as code. This is not allowed as an id in Plone, so it has always been created as id-id instead.
      This needs some special handling.
    • Fix set_recursive_language to actually find child objects. This is used to make sure that a language folder only contains content in this language.

Last maintenance release

Plone 5.2.14 is planned to be the last regular release of Plone 5.2.
This release was originally planned for October, but we moved it forward to have the security fixes in a full release. If there are good reasons, we can still make a new release.

After October 2023, Plone 5.2 is out of maintenance support.

There is still one year of security support, until October 31, 2024.
At that moment, even Python 3.8 is out of security support by the Python community.

Python compatibility

This release supports Python 2.7 and 3.8.

Python 3.6 and 3.7 should still work, but these are end of life and no longer supported.

Plone 5.2 still supports Python 2.7, but this is end-of-life since 2020. It should only be used as a temporary stepping stone before you migrate your Plone site to Python 3.

Versions of pip, zc.buildout, setuptools

In Plone core we use these versions to install Plone on Python 2:


and these on Python 3:


In general you are free to use whatever versions work for you, especially newer ones, but these worked for us.

Note that setuptools 66 is more strict with what versions it can recognize. If you run pip or buildout and it suddenly cannot find a package with a non-standard version, then this may be the cause. This is why we stayed at version 65 for Plone 5.2.


For installation instructions, see the documentation.

There is still a Unified Installer. One warning there: we could no longer test this on Python 2.7. It should work though.


If you find any issues, please report them in the main issue tracker.


If I have a Python 2.7 Plone 5.2.3 site and want to make it 'as safe as possible' without upgrading to Python 3 and or Plone 6: Is it enough to just edit buildout.cfg (and run bin/buildout) or is something needed to upgrade Zope as well ?

That should be enough. There is nothing special about the newer Zope version in here.

This should read 2024, right?

Ne he means 2023, which is correct, but there is the info missing that the security is still covered ;).

1 Like

That information is in the next line:

1 Like