Skip to main content

CMSimple CVE-2026-88418

| EUVDEUVD-2026-84857 HIGH
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-09-22 mitre GHSA-7jc4-6qrv-4984
8.8
CVSS 3.1 · Vendor: mitre
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure authenticated admin to attacker page
  2. Delivery
    Browser auto-submits forged content-save request
  3. Exploit
    CSRF no-op accepts request with admin cookie
  4. Execution
    Scripting marker stored in content/content.php
  5. Persist
    evaluate_cmsimple_scripting() runs eval() on view
  6. Impact
    Persistent RCE for all visitors

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires that CMSimple runs with its default configuration where CSRF protection is disabled (csrfProtection() is a no-op) and admin forms omit the csrf_token hidden field, and that administrator authentication is cookie-only. A victim who is a currently logged-in administrator must be induced (UI:R) to load attacker-controlled web content while holding a valid session cookie, so the forged content-save request is accepted. The attacker themselves needs no credentials (PR:N). Realistic risk is limited by the social-engineering requirement against a specific privileged, actively-authenticated user; once the scripting marker is stored in content/content.php, the eval()-based RCE then triggers automatically for all subsequent visitors including unauthenticated ones.

Impact

This is a genuine high-priority technical issue mitigated by real-world deployment factors. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) is internally consistent with the description: an unauthenticated remote attacker (PR:N) exploits a CSRF weakness (CWE-352) that requires tricking a logged-in administrator into visiting a malicious page (UI:R), ultimately achieving persistent PHP eval()-based RCE with full C:H/I:H/A:H impact. The chained outcome - CSRF → stored scripting marker → server-side eval() executed for every visitor - is severe because it converts a client-side trust flaw into persistent remote code execution. However, exploitation signals temper the urgency: EPSS is only 0.33% (26th percentile), there is no CISA KEV listing, and no vendor-confirmed public exploit. The single GitHub reference (15536818056/CVE/issues/5) may contain a writeup or PoC but this is not confirmed from the provided data. The chief limiting factor is the mandatory UI:R condition - a specific administrator must be authenticated AND socially engineered into loading attacker content while their session cookie is valid - which makes this targeted rather than mass-exploitable. Note the CPE is a placeholder ('cpe:2.3:a:n/a:n/a') and EUVD affected version is 'n/a n/a', so precise affected-version boundaries are unverified beyond the description's mention of CMSimple 5.24.

Exploit ScenarioDerived

An attacker crafts a malicious web page containing an auto-submitting form that POSTs a forged content-save request to a target CMSimple 5.24 admin endpoint, embedding a PHP scripting marker as the text payload. When a logged-in administrator visits the page, their browser silently submits the request using their session cookie; because CSRF protection is a no-op by default and no csrf_token is enforced, the marker is stored into content/content.php and thereafter executed via eval() on every page view for all visitors. No public exploit is confirmed in the provided data, though a GitHub issue reference exists.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 26, 2026

CMSimple 5.24 ships with CSRF protection disabled by default, so an unauthenticated attacker can forge a content-save request that a currently logged-in administrator's browser submits (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8), storing a text payload containing a scripting marker verbatim in content/content.php. Because evaluate_cmsimple_scripting() in functions.php subsequently runs that marker through PHP eval() on every page view, the result is persistent remote code execution on the web server for all visitors, including unauthenticated ones. There is no public exploit identified at time of analysis and the issue is not in CISA KEV; EPSS is 0.33% (26th percentile), and realistic risk is limited by the requirement to socially engineer a privileged, actively-authenticated administrator who holds a valid session cookie.

RemediationAI

No vendor-released patch identified at time of analysis, so mitigation must be applied at the deployment level. The most direct control is to turn CSRF protection back on rather than relying on the disabled default, and to add the csrf_token hidden field to every admin form plus a server-side token check on each state-changing request - this keeps the scripting feature intact but requires code changes to CMSimple core or a fork. Set the session cookie with SameSite=Strict (and Secure/HttpOnly) to stop the browser from attaching it to cross-site forged POSTs to the admin endpoint; the side effect is that some legitimate cross-site or embedded workflows will break, and browsers without SameSite support remain exposed. Additionally, place access control in front of the admin area (admin.php and related endpoints) using an IP allowlist, client certificates, or HTTP authentication at the web server or reverse proxy, and require re-authentication before content saves - this does not fix the underlying flaw but makes the forged request much harder to deliver to an authenticated session. If the CMSimple scripting feature is not required, disable or neuter the evaluate_cmsimple_scripting() path in functions.php so stored markers are never passed to eval(); this closes the RCE sink entirely but disables intended CMS scripting/plugin functionality. As a containment measure, make content/content.php non-writable by the web server between content edits (may break normal editing) and monitor the file for unexpected scripting markers, along with logging and alerting on admin POST requests that carry no valid token or arrive without a matching Origin/Referer.

Affected VersionsENISA

n/a n/a

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is CWE-352 (Cross-Site Request Forgery) compounded by an unsafe code-execution sink. CMSimple is a flat-file PHP CMS with no database: administrator authentication is cookie-only, and in version 5.24 the csrfProtection() routine is a no-op because CSRF protection is disabled in the default configuration, while admin forms also omit the csrf_token hidden field entirely. With no token validated and no Origin/Referer or SameSite enforcement on state-changing admin requests, a cross-site POST to the content-save endpoint is accepted purely on the strength of the victim's session cookie. The attack chain then abuses CMSimple's own scripting feature: text saved into content/content.php is later processed by evaluate_cmsimple_scripting() in functions.php, which passes the stored scripting marker body to PHP eval(). This converts what would otherwise be a stored-content injection into server-side code execution that fires automatically for every subsequent page view, not just for the administrator. The supplied CPE string is a placeholder (cpe:2.3:a:n/a:n/a) and the EUVD affected-version entry is 'n/a n/a', so the only version explicitly identified as affected across the intelligence sources is CMSimple 5.24 under its default configuration.

Know when PHP gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (mitre) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Attacker is unauthenticated (PR:N) but must trick a logged-in admin via CSRF (UI:R); the resulting server-side eval() RCE gives full C/I/A on the same web application (S:U).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (mitre).

CVSS VectorVendor: mitre

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
CVSS changed
Sep 26, 2026 - 00:22 NVD
8.8 (HIGH)
CVE Published
Sep 22, 2026 - 00:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 22, 2026 - 00:00 cve.org
HIGH 8.8

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

Organizations running CMSimple 5.24 face a high-severity vulnerability that could allow an attacker to achieve persistent remote code execution on the web server, affecting all site visitors and potentially allowing content alteration, malware distribution, or server compromise. Although no public exploit identified at time of analysis and exploitation requires social engineering an authenticated administrator, the potential business disruption and reputational damage make this a priority for security management. Leadership should direct immediate containment and migration planning until a vendor fix is available.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis; interim mitigations include restricting administrative interface access to trusted IP ranges, enforcing SameSite=Strict session cookies, requiring re-authentication for content saves, deploying WAF rules to block scripting markers in content-save requests, enabling CSRF protection if available in CMSimple configuration, monitoring content/content.php for unauthorized changes, and isolating or disabling CMSimple 5.24 until a vendor fix is available.

Threat Intelligence Overview

EPSS Score
0.3%
Top 74% exploitable
Prevalence
Low
niche open-source flat-file PHP CMS, small hobbyist/SMB footprint
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

More in PHP

View all
CVE-2019-11043 CRITICAL POC
9.8 Oct 28

In PHP versions 7.1.x below 7.1.33, 7.2.x below 7.2.24 and 7.3.x below 7.3.11 in certain configurations of FPM setup it

CVE-2012-1823 CRITICAL POC
9.8 May 11

sapi/cgi/cgi_main.c in PHP before 5.3.12 and 5.4.x before 5.4.2, when configured as a CGI script (aka php-cgi), does not

CVE-2016-1555 CRITICAL POC
9.8 Apr 21

(1) boardData102.php, (2) boardData103.php, (3) boardDataJP.php, (4) boardDataNA.php, and (5) boardDataWW.php in Netgear

CVE-2018-11138 CRITICAL POC
9.8 May 31

The '/common/download_agent_installer.php' script in the Quest KACE System Management Appliance 8.0.318 is accessible by

CVE-2024-11680 CRITICAL POC
9.8 Nov 26

ProjectSend versions prior to r1720 are affected by an improper authentication vulnerability. Rated critical severity (C

CVE-2025-49113 CRITICAL POC
9.9 Jun 02

Roundcube Webmail contains a critical PHP object deserialization vulnerability (CVE-2025-49113, CVSS 9.9) that allows au

CVE-2017-9841 CRITICAL POC
9.8 Jun 27

Util/PHP/eval-stdin.php in PHPUnit before 4.8.28 and 5.x before 5.6.3 allows remote attackers to execute arbitrary PHP c

CVE-2025-0108 HIGH POC
8.8 Feb 12

Palo Alto Networks PAN-OS management web interface contains an authentication bypass allowing unauthenticated attackers

CVE-2021-25298 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2021-25296 HIGH POC
8.8 Feb 15

Nagios XI version xi-5.7.5 is affected by OS command injection. Rated high severity (CVSS 8.8), this vulnerability is re

CVE-2013-4983 CRITICAL POC
10.0 Sep 10

The get_referers function in /opt/ws/bin/sblistpack in Sophos Web Appliance before 3.7.9.1 and 3.8 before 3.8.1.1 allows

CVE-2023-6553 CRITICAL POC
9.8 Dec 15

The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy