| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| Evolution CMS 3.5.8 source code.tar.gz | 2026-09-10 | 22.2 MB | |
| Evolution CMS 3.5.8 source code.zip | 2026-09-10 | 31.2 MB | |
| README.md | 2026-09-10 | 2.0 kB | |
| Totals: 3 Items | 53.4 MB | 0 | |
Evolution CMS 3.5.8
Evolution CMS 3.5.8 is a security, stability, and developer experience release for the 3.5 branch. This version hardens Manager requests, improves package/update workflows, adds stronger mail diagnostics, and expands CI coverage across modern PHP runtimes.
Highlights
- Added stricter CSRF protection for Manager actions, including legacy mutating GET actions
- Improved Manager tab restoration after login and CSRF token rotation
- Hardened security around unserialize usage, PHx,
@FILE, stored/reflected XSS vectors, empty hash login, and upgrade transport - Added template source support for database/file based template processing
- Added mail test tools, SMTP certificate verification controls, and better delivery diagnostics
- Improved package tooling with vendor publish manifest tracking and transitive dependency reporting
- Added IANA site timezone setting and improved event log timezone/actor display
- Improved Docker, installer, upgrade smoke tests, and CI coverage for PHP 8.3, 8.4, and 8.5
- Updated bundled Composer dependencies
Compatibility Note: CSRF Protection
Evolution CMS 3.5.8 tightens CSRF validation in the Manager. Some third-party or legacy packages may fail with a CSRF token mismatch error if they submit Manager forms, links, or AJAX requests without passing the current _token value or X-CSRF-TOKEN header.
The recommended fix is to update the package code to include csrf_field(), csrf_token(), or the X-CSRF-TOKEN header in Manager requests.
If a third-party package blocks access and you need a temporary compatibility workaround, comment line 76 in core/src/Middleware/VerifyCsrfToken.php:
:::php
// return $this->reject($request);
This disables the CSRF rejection response, so use it only as a short-term workaround until the affected package is updated.
The session token has changed or is missing. Reopen the manager, then review and retry your action. The action was not performed.