{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-20061 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-20061 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-20061 is a high-severity vulnerability in n/a, published on 10 Feb 2020. 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-20061 and fix it if it is affected.\n\nWhat it is: CVE-2019-20061 is a high-severity vulnerability in n/a, published on 10 Feb 2020. 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-20061 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-20061/ (Markdown: https://insights.sbomify.com/CVE-2019-20061/index.md)","id":"CVE-2019-20061","markdown":"https://insights.sbomify.com/CVE-2019-20061/index.md","name":"CVE-2019-20061","record":{"aliases":["GHSA-vgr9-p83r-mj2x"],"analysis":{"component_type":"web_application","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"YetiShare billing software","requires_auth":"none","summary":"Cleartext introduction emails in YetiShare may expose system-generated passwords, allowing attackers to read sensitive credentials if email security is not configured.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"yetishare","vendor":"mfscripts"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-319","name":"Cleartext Transmission of Sensitive Information"}],"description":"The user-introduction email in MFScripts YetiShare v3.5.2 through v4.5.4 may leak the (system-picked) password if this email is sent in cleartext. In other words, the user is not allowed to choose their own initial password.","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":"Information disclosure in n/a","id":"CVE-2019-20061","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in n/a","id":"CVE-2019-20062"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-20060"},"products":["n/a"],"published":"2020-02-10","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2019-20062","kev_date_added":null,"published":"2020-02-10"},{"cvss_score":9.1,"headline":"Weak cryptography in n/a","id":"CVE-2019-19735","kev_date_added":null,"published":"2019-12-30"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2019-20059","kev_date_added":null,"published":"2020-02-10"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2019-19734","kev_date_added":null,"published":"2019-12-30"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2019-19737","kev_date_added":null,"published":"2019-12-30"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2019-20060","kev_date_added":null,"published":"2020-02-10"}],"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":"Cleartext introduction emails in YetiShare may expose system-generated passwords, allowing attackers to read sensitive credentials if email security is not configured.","url":"https://insights.sbomify.com/CVE-2019-20061/"}