GetSimple CMS: Missing CSRF protection in UpdateCE allows forging a privileged server-side update request
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| GetSimpleCMS-CE | GetSimpleCMS-CE | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Getsimple-ce | Getsimple Cms |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.249% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Getsimple-ce
Getsimple-ce getsimple Cms |
|
| Vendors & Products |
Getsimple-ce
Getsimple-ce getsimple Cms |
| 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
|