https://vulnerability.circl.lu/sightings/feed 2026-08-30T04:16:59.442107+00:00 Vulnerability-Lookup info@circl.lu python-feedgen Contains only the most 10 recent sightings. https://vulnerability.circl.lu/sighting/bd485eca-b770-4e79-b357-a6b0d2133e15/export 2026-08-30T04:16:59.467543+00:00 Automation user https://vulnerability.circl.lu/user/automation {"uuid": "bd485eca-b770-4e79-b357-a6b0d2133e15", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-54625", "type": "seen", "source": "https://gist.github.com/alon710/818add0e0ce97b333c2bed9ff2722107", "content": "# CVE-2026-54625: CVE-2026-54625: Server-Side Page Cache Bypass and Cache Poisoning in django CMS\n\n> **CVSS Score:** 4.8\n> **Published:** 2026-08-24\n> **Full Report:** https://cvereports.com/reports/CVE-2026-54625\n\n## Summary\nPrior to version 5.0.8, django CMS fails to respect dynamically declared Vary HTTP headers in its internal page cache. This allows remote attackers to bypass authorization, leak sensitive information across user sessions, or poison the page cache by sending requests with custom headers.\n\n## TL;DR\ndjango CMS versions before 5.0.8 and 5.1.0 contain a cache key computation flaw that ignores plugin-declared HTTP Vary headers, leading to server-side cache poisoning and information disclosure.\n\n## Exploit Status: POC\n\n## Technical Details\n\n- **CWE ID**: CWE-524 / CWE-349\n- **Attack Vector**: Network\n- **CVSS v3.1 Score**: 4.8\n- **EPSS Score**: 0.00147\n- **Exploit Status**: poc\n- **KEV Status**: Not Listed\n\n## Affected Systems\n\n- django-cms\n- **django-cms**: < 5.0.8 (Fixed in: `5.0.8`)\n- **django-cms**: >= 5.1.0a1, < 5.1.0 (Fixed in: `5.1.0`)\n\n## Mitigation\n\n- Disable internal page caching by setting CMS_PAGE_CACHE = False\n- Upgrade to django CMS version 5.0.8 or 5.1.0\n- Sanitize or strip custom vary headers at the upstream reverse proxy or CDN level\n\n**Remediation Steps:**\n1. Upgrade django-cms using pip: pip install --upgrade django-cms>=5.0.8\n2. Verify the application configuration and test plugin cache partitions\n3. Clear existing cache entries using the cache backend's management tools or the Django caching API\n4. Ensure upstream CDNs or proxies are configured to prevent header injection from untrusted clients\n\n## References\n\n- [GitHub Security Advisory GHSA-fwjf-m4qw-9f2x](https://github.com/django-cms/django-cms/security/advisories/GHSA-fwjf-m4qw-9f2x)\n- [NVD CVE-2026-54625 Detail](https://nvd.nist.gov/vuln/detail/CVE-2026-54625)\n- [django CMS Pull Request 8646](https://github.com/django-cms/django-cms/pull/8646)\n- [django CMS Pull Request 8647](https://github.com/django-cms/django-cms/pull/8647)\n\n\n---\n*Generated by [CVEReports](https://cvereports.com/reports/CVE-2026-54625) - Automated Vulnerability Intelligence*", "creation_timestamp": "2026-08-25T14:31:38.973813Z"} 2026-08-25T14:31:38.973813+00:00