{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11618 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11618 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11618 is a critical vulnerability in n/a, published on 30 Apr 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-11618 and fix it if it is affected.\n\nWhat it is: CVE-2019-11618 is a critical vulnerability in n/a, published on 30 Apr 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-11618 in the wild and no public exploit code.\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-11618/ (Markdown: https://insights.sbomify.com/CVE-2019-11618/index.md)","id":"CVE-2019-11618","markdown":"https://insights.sbomify.com/CVE-2019-11618/index.md","name":"CVE-2019-11618","record":{"aliases":["GHSA-78gv-h544-mg8g"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"doorGets CMS","requires_auth":"none","summary":"Remote attackers can use hardcoded default administrator credentials to gain admin privileges and modify content in doorGets CMS.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"doorgets_cms","vendor":"doorgets"}],"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-1188","name":"Initialization of a Resource with an Insecure Default"}],"description":"doorGets 7.0 has a default administrator credential vulnerability. A remote attacker can use this vulnerability to gain administrator privileges for the creation and modification of articles via an H0XZlT44FcN1j9LTdFc5XRXhlF30UaGe1g3cZY6i1K9 access_token in a uri=blog\u0026action=index\u0026controller=blog action to /api/index.php.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Hardcoded credentials in n/a","id":"CVE-2019-11618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2019-11619"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-11617"},"products":["n/a"],"published":"2019-04-30","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-11616","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2019-11615","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-11617","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":8.2,"headline":"Path traversal in n/a","id":"CVE-2019-11608","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":8.2,"headline":"Path traversal in n/a","id":"CVE-2019-11609","kev_date_added":null,"published":"2019-04-30"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2019-11606","kev_date_added":null,"published":"2019-04-30"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Remote attackers can use hardcoded default administrator credentials to gain admin privileges and modify content in doorGets CMS.","url":"https://insights.sbomify.com/CVE-2019-11618/"}