CVE-2019-11231
CriticalPublic exploitinsufficient input sanitation in the theme-edit.php file allows upload of files with arbitrary content (PHP code, for example).
Published May 22, 2019 · Updated Jul 8, 2026
Key Facts
Patch immediately- CVE-2019-11231 is a critical-severity vulnerability (CVSS 9.8 v3.1) affecting Getsimple CMS (Get-Simple).
- It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
- EPSS estimates a 72% probability of exploitation in the next 30 days.
- Fixed versions are available, including Getsimple CMS <=3.3.15, Getsimple CMS 3.3.15.
- Brandefense priority: patch immediately, because it is very likely to be exploited soon.
CVSS v3.1
9.8
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
72%
Higher than 99.4% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2019-11231 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
An issue was discovered in GetSimple CMS through 3.3.15. insufficient input sanitation in the theme-edit.php file allows upload of files with arbitrary content (PHP code, for example). This vulnerability is triggered by an authenticated user; however, authentication can be bypassed. According to the official documentation for installation step 10, an admin is required to upload all the files, including the .htaccess files, and run a health check. However, what is overlooked is that the Apache HTTP Server by default no longer enables the AllowOverride directive, leading to data/users/admin.xml password exposure. The passwords are hashed but this can be bypassed by starting with the data/other/authorization.xml API key. This allows one to target the session state, since they decided to roll their own implementation. The cookie_name is crafted information that can be leaked from the frontend (site name and version). If a someone leaks the API key and the admin username, then they can bypass authentication. To do so, they need to supply a cookie based on an SHA-1 computation of this known information. The vulnerability exists in the admin/theme-edit.php file. This file checks for forms submissions via POST requests, and for the csrf nonce. If the nonce sent is correct, then the file provided by the user is uploaded. There is a path traversal allowing write access outside the jailed themes directory root. Exploiting the traversal is not necessary because the .htaccess file is ignored. A contributing factor is that there isn't another check on the extension before saving the file, with the assumption that the parameter content is safe. This allows the creation of web accessible and executable files with arbitrary content.
Affected Products
1 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Getsimple CMSGet-Simple | See advisory | 3.3.15 |
Patched Releases
Getsimple CMS
<=3.3.15
Timeline
Publicly disclosed
May 22, 2019
Last updated
Jul 8, 2026
Weakness Type
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
References
FAQ
Common Questions.
An issue was discovered in GetSimple CMS through 3.3.15.
Affected: Getsimple CMS (Get-Simple). The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including Getsimple CMS <=3.3.15, Getsimple CMS 3.3.15.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.
Is CVE-2019-11231 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo