{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20567 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20567 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20567 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20567 and fix it if it is affected.\n\nWhat it is: CVE-2018-20567 is a medium-severity vulnerability in n/a, published on 28 Dec 2018. 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-2018-20567 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-2018-20567/ (Markdown: https://insights.sbomify.com/CVE-2018-20567/index.md)","id":"CVE-2018-20567","markdown":"https://insights.sbomify.com/CVE-2018-20567/index.md","name":"CVE-2018-20567","record":{"aliases":["GHSA-7ghg-23h8-fj3m"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"DouPHP CMS","requires_auth":"none","summary":"Attackers can bypass installation locks to reinstall DouPHP if the lock file is unreadable, potentially compromising the site integrity.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"douphp","vendor":"douco"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.0"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"An issue was discovered in DouCo DouPHP 1.5 20181221. \\install\\index.php allows a reload of the product in opportunistic circumstances in which install.lock cannot be read.","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":"Security feature bypass in n/a","id":"CVE-2018-20567","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2018-20568"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2018-20566"},"products":["n/a"],"published":"2018-12-28","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-12564","kev_date_added":null,"published":"2019-06-02"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-20419","kev_date_added":null,"published":"2018-12-24"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2022-24131","kev_date_added":null,"published":"2022-03-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-3370","kev_date_added":null,"published":"2021-12-08"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2022-46438","kev_date_added":null,"published":"2023-01-12"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2018-20566","kev_date_added":null,"published":"2018-12-28"}],"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-09-16","vendors":["n/a"]},"summary":"Attackers can bypass installation locks to reinstall DouPHP if the lock file is unreadable, potentially compromising the site integrity.","url":"https://insights.sbomify.com/CVE-2018-20567/"}