Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Thu, 01 Oct 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | GetSimple CMS: Missing CSRF protection in UpdateCE allows forging a privileged server-side update request | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV3_1
|
Subscriptions
No data.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-01T19:38:30.623Z
Reserved: 2026-06-22T16:39:01.043Z
Link: CVE-2026-56662
No data.
Status : Deferred
Published: 2026-10-01T20:17:26.950
Modified: 2026-10-01T20:23:46.493
Link: CVE-2026-56662
No data.
OpenCVE Enrichment
Updated: 2026-10-01T20:30:04Z
-
CWE-352
Cross-Site Request Forgery (CSRF)