{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12361 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-12361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-12361 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 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-12361 and fix it if it is affected.\n\nWhat it is: CVE-2019-12361 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 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-12361 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-2019-12361/ (Markdown: https://insights.sbomify.com/CVE-2019-12361/index.md)","id":"CVE-2019-12361","markdown":"https://insights.sbomify.com/CVE-2019-12361/index.md","name":"CVE-2019-12361","record":{"aliases":["GHSA-3g6f-gvxf-2qx6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EmpireCMS","requires_auth":"none","summary":"Cross-site scripting in EmpireCMS allows attackers to execute scripts and potentially modify templates via crafted parameters.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"empirecms","vendor":"phome"}],"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"},{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"EmpireCMS 7.5.0 has XSS via the from parameter to e/member/doaction.php, as demonstrated by a CSRF payload that changes the dynamic page template. The attacker can choose to resend the e/template/member/regsend.php registered activation mail 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-2019-12361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-12362"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2019-12360"},"products":["n/a"],"published":"2019-05-27","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-28585","kev_date_added":null,"published":"2022-05-03"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2020-22937","kev_date_added":null,"published":"2021-08-17"},{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2018-20300","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2018-18869","kev_date_added":null,"published":"2018-10-31"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-18449","kev_date_added":null,"published":"2019-03-07"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-18086","kev_date_added":null,"published":"2018-10-09"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-16339","kev_date_added":null,"published":"2018-09-02"}],"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-04","vendors":["n/a"]},"summary":"Cross-site scripting in EmpireCMS allows attackers to execute scripts and potentially modify templates via crafted parameters.","url":"https://insights.sbomify.com/CVE-2019-12361/"}