{"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-2006-3935 in the wild and no public exploit code.","fix":"Upgrade org.opencms:opencms-core to 6.2.2 or later.","what":"CVE-2006-3935 is a medium-severity missing authorization vulnerability in n/a, published on 31 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-3935 and fix it if it is affected.\n\nWhat it is: CVE-2006-3935 is a medium-severity missing authorization vulnerability in n/a, published on 31 Jul 2006. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2006-3935 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 6.2.2\n- org.opencms:opencms-core (Maven): affected all versions; fixed in 6.2.2\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-2006-3935/ (Markdown: https://insights.sbomify.com/CVE-2006-3935/index.md)","id":"CVE-2006-3935","markdown":"https://insights.sbomify.com/CVE-2006-3935/index.md","name":"CVE-2006-3935","record":{"aliases":["GHSA-v3c3-qr6m-8m7m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"OpenCms CMS","requires_auth":"low_privilege","summary":"Authenticated users can bypass authorization checks to access administrative functions, allowing privilege escalation and data manipulation.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"opencms","vendor":"alkacon"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:S/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"system/workplace/views/admin/admin-main.jsp in Alkacon OpenCms before 6.2.2 does not restrict access to administrator functions, which allows remote authenticated users to (1) send broadcast messages to all users (/workplace/broadcast), (2) list all users (/accounts/users), (3) add webusers (/accounts/webusers/new), (4) upload database import and export files (/database/importhttp), (5) upload arbitrary program modules (/modules/modules_import), and (6) read the log file (/workplace/logfileview) by setting the appropriate value for the path parameter in a direct request to admin-main.jsp.","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 Improper Access Control via system/workplace/views/admin/admin-main.jsp","id":"CVE-2006-3935","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"missing_authorization","year":"2006"},"n_packages":2,"n_references":12,"next":{"headline":"Alkacon OpenCms Exposes JSP Source Code","id":"CVE-2006-3936"},"packages":[{"ecosystem":"Maven","fixed":["6.2.2"],"introduced":["0"],"last_affected":[],"package":"org.opencms:opencms-core","purl":null,"source":"GHSA-v3c3-qr6m-8m7m"},{"ecosystem":"Maven","fixed":["6.2.2"],"introduced":["0"],"last_affected":[],"package":"org.opencms:opencms-core","purl":"pkg:maven/org.opencms/opencms-core","source":"GHSA-v3c3-qr6m-8m7m"}],"prev":{"headline":"Alkacon OpenCMS Absolute Path Traversal via pathname in filePath parameter","id":"CVE-2006-3934"},"products":["n/a"],"published":"2006-07-31","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.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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Authenticated users can bypass authorization checks to access administrative functions, allowing privilege escalation and data manipulation.","url":"https://insights.sbomify.com/CVE-2006-3935/"}