{"answers":{"affected":"2 open source packages ship an affected version, including org.opencms:opencms-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11818 in the wild and no public exploit code.","fix":"Upgrade org.opencms:opencms-core to 11.0.0 or later.","what":"CVE-2019-11818 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 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-11818 and fix it if it is affected.\n\nWhat it is: CVE-2019-11818 is a medium-severity cross-site scripting vulnerability in n/a, published on 8 May 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-11818 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.opencms:opencms-core (Maven): affected all versions; fixed in 11.0.0\n- org.opencms:opencms-core (Maven): affected all versions; fixed in 11.0.0\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-11818/ (Markdown: https://insights.sbomify.com/CVE-2019-11818/index.md)","id":"CVE-2019-11818","markdown":"https://insights.sbomify.com/CVE-2019-11818/index.md","name":"CVE-2019-11818","record":{"aliases":["GHSA-c8j6-gqq8-4prj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenCMS","requires_auth":"none","summary":"Stored XSS in OpenCMS allows attackers to inject JavaScript via user profile fields, 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":"opencms","vendor":"alkacon"}],"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":"Alkacon OpenCMS v10.5.4 and before is affected by stored cross site scripting (XSS) in the module New User (/opencms/system/workplace/admin/accounts/user_new.jsp). This allows an attacker to insert arbitrary JavaScript as user input (First Name or Last Name), which will be executed whenever the affected snippet is loaded.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Alkacon OpenCMS XSS via New User module","id":"CVE-2019-11818","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"xss","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Alkacon OpenCMS CSV Injection via New User module","id":"CVE-2019-11819"},"packages":[{"ecosystem":"Maven","fixed":["11.0.0"],"introduced":["0"],"last_affected":[],"package":"org.opencms:opencms-core","purl":null,"source":"GHSA-c8j6-gqq8-4prj"},{"ecosystem":"Maven","fixed":["11.0.0"],"introduced":["0"],"last_affected":[],"package":"org.opencms:opencms-core","purl":"pkg:maven/org.opencms/opencms-core","source":"GHSA-c8j6-gqq8-4prj"}],"prev":{"headline":"Privilege escalation in n/a","id":"CVE-2019-11816"},"products":["n/a"],"published":"2019-05-08","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-8811","kev_date_added":null,"published":"2018-03-20"},{"cvss_score":7.8,"headline":"Alkacon OpenCMS CSV Injection via New User module","id":"CVE-2019-11819","kev_date_added":null,"published":"2019-05-08"},{"cvss_score":6.8,"headline":"Cross-site scripting in n/a","id":"CVE-2005-4475","kev_date_added":null,"published":"2005-12-22"},{"cvss_score":6.5,"headline":"OpenCMS Cross-Site Scripting vulnerability","id":"CVE-2024-42699","kev_date_added":null,"published":"2025-04-21"},{"cvss_score":6.5,"headline":"XML External Entity Reference in org.opencms:opencms-core","id":"CVE-2021-3312","kev_date_added":null,"published":"2021-10-08"},{"cvss_score":6.5,"headline":"Alkacon OpenCMS Improper Access Control via system/workplace/views/admin/admin-main.jsp","id":"CVE-2006-3935","kev_date_added":null,"published":"2006-07-31"},{"cvss_score":6.4,"headline":"Cross-Site Scripting stored in Alkacon OpenCMS","id":"CVE-2024-5520","kev_date_added":null,"published":"2024-05-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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-04","vendors":["n/a"]},"summary":"Stored XSS in OpenCMS allows attackers to inject JavaScript via user profile fields, potentially leading to session hijacking or malicious actions.","url":"https://insights.sbomify.com/CVE-2019-11818/"}