{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10226 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10226 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10226 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Jun 2019. 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-2019-10226 and fix it if it is affected.\n\nWhat it is: CVE-2019-10226 is a medium-severity cross-site scripting vulnerability in n/a, published on 10 Jun 2019. 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-2019-10226 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-10226/ (Markdown: https://insights.sbomify.com/CVE-2019-10226/index.md)","id":"CVE-2019-10226","markdown":"https://insights.sbomify.com/CVE-2019-10226/index.md","name":"CVE-2019-10226","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Fat Free CRM","requires_auth":"none","summary":"Authenticated attackers can inject HTML into comments, potentially leading to cross-site scripting attacks despite vendor disputes.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fat_free_crm","vendor":"fatfreecrm"}],"cvss":{"score":5.4,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"HTML Injection has been discovered in the v0.19.0 version of the Fat Free CRM product via an authenticated request to the /comments URI. NOTE: the vendor disputes the significance of this report because some HTML formatting (such as with an H1 element) is allowed, but there is a XSS protection mechanism.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-03-28","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-03-28","kind":"exploitdb","ref":"46617","stars":null,"title":"Fat Free CRM 0.19.0 - HTML Injection"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2019-10226","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":5,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-10227"},"packages":[],"prev":{"headline":"Information disclosure in atomic-openshift","id":"CVE-2019-10225"},"products":["n/a"],"published":"2019-06-10","related":[{"cvss_score":6.8,"headline":"Fat Free CRM Cross-Site Request Forgery vulnerability","id":"CVE-2015-1585","kev_date_added":null,"published":"2015-02-19"},{"cvss_score":6.8,"headline":"Fat Free CRM contains Cross-site Request Forgery vulnerablilities","id":"CVE-2013-7223","kev_date_added":null,"published":"2014-01-02"},{"cvss_score":6.5,"headline":"Fat Free CRM vulnerable to SQL Injection","id":"CVE-2013-7225","kev_date_added":null,"published":"2014-01-02"},{"cvss_score":6.1,"headline":"Cross-site scripting in fat_free_crm","id":"CVE-2018-20975","kev_date_added":null,"published":"2019-08-20"},{"cvss_score":5,"headline":"Fat Free CRM has fixed token value","id":"CVE-2013-7222","kev_date_added":null,"published":"2014-01-02"},{"cvss_score":5,"headline":"Fat Free CRM allows remote attackers to obtain sensitive information via a direct request","id":"CVE-2013-7224","kev_date_added":null,"published":"2014-01-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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Authenticated attackers can inject HTML into comments, potentially leading to cross-site scripting attacks despite vendor disputes.","url":"https://insights.sbomify.com/CVE-2019-10226/"}