CSRF issue around publishing of draft changes in Django CMS. Versions affected are Django CMS <3.0.14 and <3.1.1. Upstream patch: https://github.com/divio/django-cms/commit/f77cbc607d6e2a62e63287d37ad320109a2cc78a References: http://www.openwall.com/lists/oss-security/2015/06/27/1 https://www.django-cms.org/en/blog/2015/06/27/311-3014-release/
Created Django14 tracking bugs for this issue: Affects: epel-6 [bug 1484981] Created python-django tracking bugs for this issue: Affects: epel-7 [bug 1484979] Affects: fedora-all [bug 1484980]
I may be wrong, you filed a bug against python-django, which is the framework. The CVE is for python-django-cms, which is a different software. As far as I can see, there is no python-django-cms in Fedora or EPEL.
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2015-5081