Release | April 26, 2017

django CMS security updates

Security releases for django CMS versions 3.4 and 3.3 address medium-level vulnerabilities. We recommend updating to version 3.4.3 or 3.3.4.

5 minutes read

These updates prevent:

  • a potential escalation of privileges through a django CMS page's Advanced Settings.
  • a potential phishing attack using redirects from the login form

The updated releases are now available from our GitHub repository and PyPI.

Divio Cloud users can update their django CMS installations via the control panel.

Please see the notes on GitHub for more details.

Thanks to Anthony Steinhauser and Mark Walker for the reports.

As ever, we remind our users and contributors that all security reports, patches and concerns be addressed only to our security team by email, at [email protected].

Please do not use GitHub, our email lists or IRC to report, address or otherwise discuss matters relating to security.

django CMS SLAs for critical applications

Do you use django CMS in a critically-important application? Please contact Divio for details of SLAs, that will give you access to patches and information about vulnerabilities before disclosures or releases are made public.

Enterprise Services

Mike Barrett

Article

The next chapter of django CMS starts with our members, past, present and future.

Mike Barrett, elected President of the django CMS Association for 2026 to 2028, thanks Mario Colombo and Joel Burch and sets out three priorities: a more valuable membership, an easier choice for agencies, and meeting in person at DjangoCon Europe.

Article

Hunting Down Quadratic Loops in django CMS

How PR #8913 removed quadratic work from django CMS menus, plugins, and page permissions: a permission-heavy menu on a 4,000-page site went from 11.7 seconds to 105 ms.

Article

One operation, three interfaces: a service architecture for django CMS

How shared content operations could support editors, REST integrations, and AI tools.