{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-6889 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-6889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-6889 is a high-severity vulnerability in n/a, published on 12 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-6889 and fix it if it is affected.\n\nWhat it is: CVE-2018-6889 is a high-severity vulnerability in n/a, published on 12 Feb 2018. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-6889 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-6889/ (Markdown: https://insights.sbomify.com/CVE-2018-6889/index.md)","id":"CVE-2018-6889","markdown":"https://insights.sbomify.com/CVE-2018-6889/index.md","name":"CVE-2018-6889","record":{"aliases":["GHSA-9wwh-m593-xcgx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Typesetter CMS","requires_auth":"low_privilege","summary":"Attackers can poison web caches, perform password reset attacks, or redirect users via Host header injection in Typesetter.","user_interaction":"not_required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"typesetter","vendor":"typesettercms"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"An issue was discovered in Typesetter 5.1. It suffers from a Host header injection vulnerability, Using this attack, a malicious user can poison the web cache or perform advanced password reset attacks or even trigger arbitrary user re-direction.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-02-13","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-02-13","kind":"exploitdb","ref":"44028","stars":null,"title":"TypeSetter CMS 5.1 - 'Host' Header Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Open redirect in n/a","id":"CVE-2018-6889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"open_redirect","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-6890"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2018-6888"},"products":["n/a"],"published":"2018-02-12","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2022-25523","kev_date_added":null,"published":"2022-03-25"},{"cvss_score":8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-6888","kev_date_added":null,"published":"2018-02-12"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2020-25790","kev_date_added":null,"published":"2020-09-19"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-19511","kev_date_added":null,"published":"2021-06-21"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2018-16639","kev_date_added":null,"published":"2019-05-13"},{"cvss_score":4.8,"headline":"Typesetter CMS Reflected XSS via Editing.php","id":"CVE-2025-71164","kev_date_added":null,"published":"2026-01-14"}],"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":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can poison web caches, perform password reset attacks, or redirect users via Host header injection in Typesetter.","url":"https://insights.sbomify.com/CVE-2018-6889/"}