{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26251 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26251 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26251 is a medium-severity vulnerability in open-zaak, published on 18 Dec 2020. 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-2020-26251 and fix it if it is affected.\n\nWhat it is: CVE-2020-26251 is a medium-severity vulnerability in open-zaak, published on 18 Dec 2020. 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-2020-26251 in the wild and no public exploit code.\n\nAffected product: open-zaak. 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-2020-26251/ (Markdown: https://insights.sbomify.com/CVE-2020-26251/index.md)","id":"CVE-2020-26251","markdown":"https://insights.sbomify.com/CVE-2020-26251/index.md","name":"CVE-2020-26251","record":{"aliases":["GHSA-chhr-gxrg-64x7"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Open Zaak case management","requires_auth":"none","summary":"Open Zaak had overly permissive CORS settings allowing cross-origin requests, though mitigated by other security controls, requiring an upgrade to secure defaults.","user_interaction":"required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"open_zaak","vendor":"openzaak"}],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-346","name":"Origin Validation Error"}],"description":"Open Zaak is a modern, open-source data- and services-layer to enable zaakgericht werken, a Dutch approach to case management. In Open Zaak before version 1.3.3 the Cross-Origin-Resource-Sharing policy in Open Zaak is currently wide open - every client is allowed. This allows evil.com to run scripts that perform AJAX calls to known Open Zaak installations, and the browser will not block these. This was intended to only apply to development machines running on localhost/127.0.0.1. Open Zaak 1.3.3 disables CORS by default, while it can be opted-in through environment variables. The vulnerability does not actually seem exploitable because: a) The session cookie has a `Same-Site: Lax` policy which prevents it from being sent along in Cross-Origin requests. b) All pages that give access to (production) data are login-protected c) `Access-Control-Allow-Credentials` is set to `false` d) CSRF checks probably block the remote origin, since they're not explicitly added to the trusted allowlist.","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":"CORS configuration is possibly vulnerable","id":"CVE-2020-26251","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"misconfiguration","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Layout XML RCE Vulnerability in OpenMage","id":"CVE-2020-26252"},"packages":[],"prev":{"headline":"Base class whitelist configuration ignored in OAuthenticator","id":"CVE-2020-26250"},"products":["open-zaak"],"published":"2020-12-18","related":[],"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":["open-zaak"]},"summary":"Open Zaak had overly permissive CORS settings allowing cross-origin requests, though mitigated by other security controls, requiring an upgrade to secure defaults.","url":"https://insights.sbomify.com/CVE-2020-26251/"}