{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-35740 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-35740 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-35740 is a medium-severity vulnerability in Dotcms Dotcms, published on 10 Nov 2022. 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-2022-35740 and fix it if it is affected.\n\nWhat it is: CVE-2022-35740 is a medium-severity vulnerability in Dotcms Dotcms, published on 10 Nov 2022. 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-2022-35740 in the wild and no public exploit code.\n\nAffected product: Dotcms Dotcms. 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-2022-35740/ (Markdown: https://insights.sbomify.com/CVE-2022-35740/index.md)","id":"CVE-2022-35740","markdown":"https://insights.sbomify.com/CVE-2022-35740/index.md","name":"CVE-2022-35740","record":{"aliases":["GHSA-qv8m-37rr-fj54"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"dotCMS content management","requires_auth":"none","summary":"Attackers can bypass access controls and view restricted content by using semicolons in URLs to evade path-based security filters in dotCMS.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"dotcms","vendor":"dotcms"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"dotCMS before 22.06 allows remote attackers to bypass intended access control and obtain sensitive information by using a semicolon in a URL to introduce a matrix parameter. (This is also fixed in 5.3.8.12, 21.06.9, and 22.03.2 for LTS users.) Some Java application frameworks, including those used by Spring or Tomcat, allow the use of matrix parameters: these are URI parameters separated by semicolons. Through precise semicolon placement in a URI, it is possible to exploit this feature to avoid dotCMS's path-based XSS prevention (such as \"require login\" filters), and consequently access restricted resources. For example, an attacker could place a semicolon immediately before a / character that separates elements of a filesystem path. This could reveal file content that is ordinarily only visible to signed-in users. This issue can be chained with other exploit code to achieve XSS attacks against dotCMS.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in n/a","id":"CVE-2022-35740","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"dotcms:dotcms","products":["dotcms:dotcms"],"type":"security_feature_bypass","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Apache CloudStack SAML Single Sign-On XXE","id":"CVE-2022-35741"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-35739"},"products":["n/a"],"published":"2022-11-10","related":[{"cvss_score":9.8,"headline":"dotCMS Unrestricted Upload of File","id":"CVE-2022-26352","kev_date_added":"2022-08-25","published":"2022-07-17"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2020-19138","kev_date_added":null,"published":"2021-09-08"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2020-6754","kev_date_added":null,"published":"2020-02-05"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2017-5344","kev_date_added":null,"published":"2017-02-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-2355","kev_date_added":null,"published":"2016-12-19"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2016-8902","kev_date_added":null,"published":"2016-11-14"},{"cvss_score":9.4,"headline":"Code injection in dotCMS","id":"CVE-2025-11165","kev_date_added":null,"published":"2026-02-24"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-01","vendors":["n/a"]},"summary":"Attackers can bypass access controls and view restricted content by using semicolons in URLs to evade path-based security filters in dotCMS.","url":"https://insights.sbomify.com/CVE-2022-35740/"}