CMSimple 5.24 CSRF Protection content/content.php evaluate_cmsimple_scripting cross-site request forgery

Summaryinfo

A vulnerability, which was classified as problematic, has been found in CMSimple 5.24. This impacts the function evaluate_cmsimple_scripting of the file content/content.php of the component CSRF protection. This manipulation causes cross-site request forgery. This vulnerability appears as CVE-2026-88418. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in CMSimple 5.24 and classified as problematic. Affected by this vulnerability is the function evaluate_cmsimple_scripting of the file content/content.php of the component CSRF Protection. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. As an impact it is known to affect integrity. The summary by CVE is:

CMSimple 5.24 ships with CSRF protection disabled by default, which turns csrfProtection() into a no-op on every state-changing admin request, and it does not send the csrf_token hidden field in admin forms. Because administrator authentication is cookie-only and no CSRF token is enforced, an unauthenticated attacker can induce a logged-in administrator's browser to issue a forged content-save request with a text payload containing a scripting marker. The marker is stored verbatim into content/content.php; on every subsequent page view evaluate_cmsimple_scripting() (functions.php) executes the marker body with PHP eval() — for all visitors, including unauthenticated ones. This yields persistent remote code execution on the web server.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-88418 since 09/10/2026. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details of the vulnerability are known, but there is no available exploit.

By approaching the search of inurl:content/content.php it is possible to find vulnerable targets with Google Hacking.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Name

• CMSimple

Version

• 5.24

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion