{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-19598 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-19598 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-19598 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Dec 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-19598 and fix it if it is affected.\n\nWhat it is: CVE-2018-19598 is a medium-severity cross-site scripting vulnerability in n/a, published on 19 Dec 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-19598 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-19598/ (Markdown: https://insights.sbomify.com/CVE-2018-19598/index.md)","id":"CVE-2018-19598","markdown":"https://insights.sbomify.com/CVE-2018-19598/index.md","name":"CVE-2018-19598","record":{"aliases":["GHSA-5hqq-vj6p-3gqf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Statamic CMS","requires_auth":"high_privilege","summary":"An attacker can inject malicious scripts via user profile fields in Statamic, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"statamic","vendor":"statamic"}],"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":"Statamic 2.10.3 allows XSS via First Name or Last Name to the /users URI in an 'Add new user' request.","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-19598","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-19599"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-19597"},"products":["n/a"],"published":"2018-12-19","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2021-45364","kev_date_added":null,"published":"2022-02-10"},{"cvss_score":9.3,"headline":"Statamic is vulnerable to account takeover via password reset link injection","id":"CVE-2026-27593","kev_date_added":null,"published":"2026-02-24"},{"cvss_score":8.8,"headline":"Statamic allows Authenticated Control Panel users to escalate privileges via elevated session bypass","id":"CVE-2026-27939","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":8.8,"headline":"Remote code execution via form uploads in statamic/cms","id":"CVE-2023-48217","kev_date_added":null,"published":"2023-11-14"},{"cvss_score":8.8,"headline":"Statamic framework Incorrect Permission Assignment","id":"CVE-2017-11422","kev_date_added":null,"published":"2017-07-24"},{"cvss_score":8.7,"headline":"Statamic has Stored XSS via SVG Sanitization Bypass","id":"CVE-2026-33172","kev_date_added":null,"published":"2026-03-20"},{"cvss_score":8.7,"headline":"Statamic vulnerable to privilege escalation via stored cross-site scripting","id":"CVE-2026-28426","kev_date_added":null,"published":"2026-02-27"}],"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":"An attacker can inject malicious scripts via user profile fields in Statamic, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2018-19598/"}