{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17233 exists.","fix":"No fix has been published for CVE-2019-17233 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17233 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Oct 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-17233 and fix it if it is affected.\n\nWhat it is: CVE-2019-17233 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 Oct 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-17233 exists.\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-17233/ (Markdown: https://insights.sbomify.com/CVE-2019-17233/index.md)","id":"CVE-2019-17233","markdown":"https://insights.sbomify.com/CVE-2019-17233/index.md","name":"CVE-2019-17233","record":{"aliases":["GHSA-5r74-p252-mh8w"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"WordPress plugin","requires_auth":"none","summary":"An attacker can inject malicious HTML into the ultimate-faqs WordPress plugin, potentially leading to cross-site scripting attacks.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ultimate_faq","vendor":"etoilewebdesign"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"Functions/EWD_UFAQ_Import.php in the ultimate-faqs plugin through 1.8.24 for WordPress allows HTML content injection.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2019/CVE-2019-17233.yaml","stars":null,"title":"WordPress Ultimate FAQs \u003c= 1.8.24 – Unauthenticated HTML Content Injection"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2019-17233","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-17234"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2019-17232"},"products":["n/a"],"published":"2019-10-07","related":[{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2019-17232","kev_date_added":null,"published":"2019-10-07"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2020-7107","kev_date_added":null,"published":"2020-01-16"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2019-15643","kev_date_added":null,"published":"2019-08-27"},{"cvss_score":5.7,"headline":"Ultimate FAQ \u003c 2.1.2 - Subscriber+ Arbitrary FAQ Creation","id":"CVE-2021-24968","kev_date_added":null,"published":"2022-01-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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can inject malicious HTML into the ultimate-faqs WordPress plugin, potentially leading to cross-site scripting attacks.","url":"https://insights.sbomify.com/CVE-2019-17233/"}