{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-18259 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-18259 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-18259 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Oct 2018. 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-2018-18259 and fix it if it is affected.\n\nWhat it is: CVE-2018-18259 is a medium-severity cross-site scripting vulnerability in n/a, published on 15 Oct 2018. 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-2018-18259 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-18259/ (Markdown: https://insights.sbomify.com/CVE-2018-18259/index.md)","id":"CVE-2018-18259","markdown":"https://insights.sbomify.com/CVE-2018-18259/index.md","name":"CVE-2018-18259","record":{"aliases":["GHSA-h7hf-q55c-77v2"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"LUYA CMS","requires_auth":"none","summary":"Stored XSS in LUYA CMS allows attackers to inject malicious scripts via the admin API, 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":"luya_cms","vendor":"luya"}],"cvss":{"score":6.1,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/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":"Stored XSS has been discovered in version 1.0.12 of the LUYA CMS software via /admin/api-cms-nav/create-page.","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-18259","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Camaleon CMS vulnerable to Stored Cross-site Scripting","id":"CVE-2018-18260"},"packages":[],"prev":{"headline":"Code injection in n/a","id":"CVE-2018-18258"},"products":["n/a"],"published":"2018-10-15","related":[],"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":"Stored XSS in LUYA CMS allows attackers to inject malicious scripts via the admin API, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2018-18259/"}