{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-19889 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-19889 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-19889 is a high-severity vulnerability in n/a, published on 24 Aug 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-19889 and fix it if it is affected.\n\nWhat it is: CVE-2020-19889 is a high-severity vulnerability in n/a, published on 24 Aug 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-19889 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-2020-19889/ (Markdown: https://insights.sbomify.com/CVE-2020-19889/index.md)","id":"CVE-2020-19889","markdown":"https://insights.sbomify.com/CVE-2020-19889/index.md","name":"CVE-2020-19889","record":{"aliases":["GHSA-4842-pw8g-w8wv"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"DBHcms CMS","requires_auth":"none","summary":"Attackers can force authenticated users to create new accounts via CSRF, leading to unauthorized access and privilege escalation in DBHcms.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dbhcms","vendor":"dbhcms_project"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"DBHcms v1.2.0 has no CSRF protection mechanism,as demonstrated by CSRF for index.php?dbhcms_pid=-70 can add a user.","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":"Cross-site request forgery in n/a","id":"CVE-2020-19889","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Path traversal in n/a","id":"CVE-2020-19890"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-19888"},"products":["n/a"],"published":"2020-08-24","related":[{"cvss_score":8.1,"headline":"Cross-site request forgery in n/a","id":"CVE-2020-19886","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2020-19878","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":7.2,"headline":"File upload in n/a","id":"CVE-2020-19891","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-19879","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-19880","kev_date_added":null,"published":"2020-08-24"},{"cvss_score":5.9,"headline":"Missing authorization in n/a","id":"CVE-2020-19888","kev_date_added":null,"published":"2020-08-24"}],"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":"Attackers can force authenticated users to create new accounts via CSRF, leading to unauthorized access and privilege escalation in DBHcms.","url":"https://insights.sbomify.com/CVE-2020-19889/"}