All vulnerabilities
CVE-2026-56662GHSA-2rxv-4g4m-573w

GetSimpleCMS-CE: GetSimple CMS: Missing CSRF protection in UpdateCE allows forging a privileged server-side update request

GetSimpleCMS-CE GetSimpleCMS-CE
CVSS
9.6Critical
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 6 Oct 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.22%Chance of exploitation activity in the next 30 days, higher than 11% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in1.5Fixed versionGitHub
Published1 Oct 2026Updated 6 Oct 2026CVE List

What fixes it

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

Description

GetSimple CMS is a content management system (CMS), and GetSimple CMS CE is the community edition of that CMS. Prior to version 1.5, the UpdateCE update form contained no anti-CSRF token, and the POST handler performed no token or request-origin verification. A remote attacker can host a page that auto-submits a forged POST to the update endpoint; when an authenticated administrator visits it, the server performs an attacker-directed download-and-deploy operation in the administrator's session — with no further interaction. Because the deployed content is executed (see the related ZIP-extraction advisory), this yields remote code execution. The url field is additionally written into the form unescaped, providing a secondary HTML-injection sink via a malicious upgrade.json. This issue has been patched in version 1.5.

Text from CVE List

Affected versions 2

  • GetSimpleCMS-CEaffected: < 1.5CVE List
  • UpdateCE, php<= 1.4GitHub

References 1