CVE-2026-56662 GetSimple CMS: Missing CSRF protection in UpdateCE allows forging a privileged server-side update request
A missing CSRF token in GetSimple CMS allows attackers to force administrators to execute remote code via forged update requests.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- None listed
What is CVE-2026-56662?
CVE-2026-56662 is a critical vulnerability in GetSimpleCMS-CE, published on 1 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-352
Which versions are affected by CVE-2026-56662?
How do I fix CVE-2026-56662?
No fix has been published for CVE-2026-56662 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-56662 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56662 exists.