CVE-2026-56662: GetSimple CMS: Missing CSRF protection in UpdateCE allows forging a privileged server-side update request
Affected: GetSimpleCMS-CE · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 16% of scored CVEs
DescriptionCVE.org
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.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- GetSimpleCMS-CE · GetSimpleCMS-CE< 1.5
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Cross-Site Request Forgery
- Vendor
- GetSimpleCMS-CE
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-56662 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.