{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-11209 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-11209 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-11209 is a high-severity vulnerability in n/a, published on 16 May 2018. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-11209 and fix it if it is affected.\n\nWhat it is: CVE-2018-11209 is a high-severity vulnerability in n/a, published on 16 May 2018. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-11209 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-11209/ (Markdown: https://insights.sbomify.com/CVE-2018-11209/index.md)","id":"CVE-2018-11209","markdown":"https://insights.sbomify.com/CVE-2018-11209/index.md","name":"CVE-2018-11209","record":{"aliases":["GHSA-hvj4-mm2p-82f7"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Z-BlogPHP CMS","requires_auth":"high_privilege","summary":"Z-BlogPHP uses MD5 for password verification, allowing attackers to bypass access restrictions via dictionary or rainbow-table attacks.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"z-blogphp","vendor":"zblogcn"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"description":"An issue was discovered in Z-BlogPHP 2.0.0. zb_system/cmd.php?act=verify relies on MD5 for the password parameter, which might make it easier for attackers to bypass intended access restrictions via a dictionary or rainbow-table attack. NOTE: the vendor declined to accept this as a valid issue","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":"Weak cryptography in n/a","id":"CVE-2018-11209","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2018-11210"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-11208"},"products":["n/a"],"published":"2018-05-16","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2024-55529","kev_date_added":null,"published":"2025-01-06"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-40357","kev_date_added":null,"published":"2022-09-20"},{"cvss_score":9.1,"headline":"Path traversal in n/a","id":"CVE-2020-29177","kev_date_added":null,"published":"2021-12-02"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-19463","kev_date_added":null,"published":"2018-11-22"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-18842","kev_date_added":null,"published":"2018-10-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-8893","kev_date_added":null,"published":"2018-03-31"},{"cvss_score":7.8,"headline":"File upload in n/a","id":"CVE-2020-29176","kev_date_added":null,"published":"2021-12-02"}],"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-05","vendors":["n/a"]},"summary":"Z-BlogPHP uses MD5 for password verification, allowing attackers to bypass access restrictions via dictionary or rainbow-table attacks.","url":"https://insights.sbomify.com/CVE-2018-11209/"}