{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-8811 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-8811 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-8811 is a high-severity vulnerability in n/a, published on 20 Mar 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-8811 and fix it if it is affected.\n\nWhat it is: CVE-2018-8811 is a high-severity vulnerability in n/a, published on 20 Mar 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-8811 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-8811/ (Markdown: https://insights.sbomify.com/CVE-2018-8811/index.md)","id":"CVE-2018-8811","markdown":"https://insights.sbomify.com/CVE-2018-8811/index.md","name":"CVE-2018-8811","record":{"aliases":["GHSA-vvf5-p2rf-hgq3"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenCMS","requires_auth":"none","summary":"Remote attackers can hijack administrative sessions via CSRF to escalate privileges in OpenCMS, requiring a registered content manager account for exploitation.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opencms","vendor":"alkacon"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-site request forgery (CSRF) vulnerability in system/workplace/admin/accounts/user_role.jsp in OpenCMS 10.5.3 allows remote attackers to hijack the authentication of administrative users for requests that perform privilege escalation. Note: It is argued that OpenCMS allows only registered users to upload different kind of content artifacts (SVG, .doc, .docx). The uploaded content is stored in the CMS content repository \"as is\". In case of scripts inside an SVG, this may or may not be \"malicious\", there is no way of knowing if the uploaded SVG contains the script for a reason. To exploit the \"issue\", a user must have an account in the CMS as a content manager","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2018-04-02","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2018-04-02","kind":"exploitdb","ref":"44391","stars":null,"title":"OpenCMS 10.5.3 - Cross-Site Request Forgery"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2018-8811","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Open redirect in n/a","id":"CVE-2018-8813"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2018-8810"},"products":["n/a"],"published":"2018-03-20","related":[{"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":"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Remote attackers can hijack administrative sessions via CSRF to escalate privileges in OpenCMS, requiring a registered content manager account for exploitation.","url":"https://insights.sbomify.com/CVE-2018-8811/"}