{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19170 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19170 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19170 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Nov 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-19170 and fix it if it is affected.\n\nWhat it is: CVE-2018-19170 is a medium-severity cross-site scripting vulnerability in n/a, published on 11 Nov 2018. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-19170 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-19170/ (Markdown: https://insights.sbomify.com/CVE-2018-19170/index.md)","id":"CVE-2018-19170","markdown":"https://insights.sbomify.com/CVE-2018-19170/index.md","name":"CVE-2018-19170","record":{"aliases":["GHSA-x766-6xph-9whf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"JPress CMS","requires_auth":"high_privilege","summary":"Stored XSS in JPress admin settings allows attackers to inject scripts, potentially leading to session hijacking or malicious actions.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jpress","vendor":"jpress"}],"cvss":{"score":4.8,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N","version":"3.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"In JPress v1.0-rc.5, there is stored XSS via each of the first three input fields to the starter-tomcat-1.0/admin/setting URI, as demonstrated by the web_name parameter.","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 scripting in n/a","id":"CVE-2018-19170","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19178"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-19168"},"products":["n/a"],"published":"2018-11-11","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-50919","kev_date_added":null,"published":"2024-11-18"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-45807","kev_date_added":null,"published":"2022-01-13"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2024-43033","kev_date_added":null,"published":"2024-08-22"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2022-23330","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2021-46114","kev_date_added":null,"published":"2022-01-26"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2021-45808","kev_date_added":null,"published":"2022-01-19"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2021-45806","kev_date_added":null,"published":"2022-01-13"}],"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-09-16","vendors":["n/a"]},"summary":"Stored XSS in JPress admin settings allows attackers to inject scripts, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2018-19170/"}