{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11231 exists.","fix":"No fix has been published for CVE-2019-11231 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11231 is a critical vulnerability in n/a, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-11231 and fix it if it is affected.\n\nWhat it is: CVE-2019-11231 is a critical vulnerability in n/a, published on 22 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-11231 exists.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-11231/ (Markdown: https://insights.sbomify.com/CVE-2019-11231/index.md)","id":"CVE-2019-11231","markdown":"https://insights.sbomify.com/CVE-2019-11231/index.md","name":"CVE-2019-11231","record":{"aliases":["GHSA-hx55-22f6-mp64"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":true,"product_category":"GetSimple CMS","requires_auth":"none","summary":"Authenticated attackers can upload arbitrary PHP files via theme editor, leading to remote code execution, especially if default Apache configurations expose sensitive data.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"getsimple_cms","vendor":"get-simple"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-04-28","github_poc":1,"max_poc_stars":1,"metasploit":1,"nuclei":0,"refs":[{"date":"2025-12-20T13:13:25Z","kind":"github_poc","ref":"https://github.com/akincibor/CVE-2019-11231-PoC","stars":1,"title":"CVE-2019-11231 PoC"},{"date":"2019-04-28","kind":"metasploit","ref":"exploit/multi/http/getsimplecms_unauth_code_exec","stars":null,"title":"GetSimpleCMS Unauthenticated RCE"},{"date":"2019-05-20","kind":"exploitdb","ref":"46880","stars":null,"title":"GetSimpleCMS - Unauthenticated Remote Code Execution (Metasploit)"}],"tier":"weaponised"},"has_fix":false,"headline":"File upload in n/a","id":"CVE-2019-11231","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-11232"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2019-11230"},"products":["n/a"],"published":"2019-05-22","related":[{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2022-41544","kev_date_added":null,"published":"2022-10-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-17103","kev_date_added":null,"published":"2018-09-16"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2014-8722","kev_date_added":null,"published":"2017-03-17"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-23839","kev_date_added":null,"published":"2020-09-01"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2013-1420","kev_date_added":null,"published":"2020-01-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2018-16325","kev_date_added":null,"published":"2018-09-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"BSD-3-Clause","name":"Metasploit"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can upload arbitrary PHP files via theme editor, leading to remote code execution, especially if default Apache configurations expose sensitive data.","url":"https://insights.sbomify.com/CVE-2019-11231/"}