{"answers":{"affected":"3 open source packages ship an affected version, including silverstripe/framework and silverstripe. It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26138 in the wild and no public exploit code.","fix":"Upgrade silverstripe/framework to 4.7.4 or later.","what":"CVE-2020-26138 is a medium-severity missing authorization vulnerability in Silverstripe Silverstripe, published on 8 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-26138 and fix it if it is affected.\n\nWhat it is: CVE-2020-26138 is a medium-severity missing authorization vulnerability in Silverstripe Silverstripe, published on 8 Jun 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2020-26138 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 4.7.4\n- silverstripe/framework (Packagist): affected from 3.0.0; fixed in 4.7.4\n- silverstripe (Bitnami): affected all versions up to 4.6.0-rc1; fixed in 4.6.0\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-26138/ (Markdown: https://insights.sbomify.com/CVE-2020-26138/index.md)","id":"CVE-2020-26138","markdown":"https://insights.sbomify.com/CVE-2020-26138/index.md","name":"CVE-2020-26138","record":{"aliases":["BIT-silverstripe-2020-26138","GHSA-7mv4-4xpg-xq44"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SilverStripe CMS","requires_auth":"none","summary":"Attackers can bypass form validation by using square brackets in field names, potentially submitting invalid or malicious data.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"silverstripe","vendor":"silverstripe"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"In SilverStripe through 4.6.0-rc1, a FormField with square brackets in the field name skips validation.","ecosystems":["Bitnami","Packagist"],"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":"FormField with square brackets in field name skips validation","id":"CVE-2020-26138","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"silverstripe:silverstripe","products":["silverstripe:silverstripe"],"type":"missing_authorization","year":"2020"},"n_packages":3,"n_references":4,"next":{"headline":"Missing authorization in n/a","id":"CVE-2020-26139"},"packages":[{"ecosystem":"Bitnami","fixed":["4.6.0"],"introduced":["0","4.6.0-rc1"],"last_affected":["4.6.0-rc1"],"package":"silverstripe","purl":"pkg:bitnami/silverstripe","source":"BIT-silverstripe-2020-26138"},{"ecosystem":"Packagist","fixed":["4.7.4"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":null,"source":"GHSA-7mv4-4xpg-xq44"},{"ecosystem":"Packagist","fixed":["4.7.4"],"introduced":["3.0.0"],"last_affected":[],"package":"silverstripe/framework","purl":"pkg:composer/silverstripe/framework","source":"GHSA-7mv4-4xpg-xq44"}],"prev":{"headline":"CRLF injection in urllib3","id":"CVE-2020-26137"},"products":["n/a"],"published":"2021-06-08","related":[{"cvss_score":10,"headline":"Other in n/a","id":"CVE-2007-2321","kev_date_added":null,"published":"2007-04-27"},{"cvss_score":9.8,"headline":"Missing warning can lead to unauthenticated admin access in SilverStripe","id":"CVE-2019-12204","kev_date_added":null,"published":"2019-09-25"},{"cvss_score":9.8,"headline":"Silverstripe Framework SQLi Vulnerability","id":"CVE-2019-5715","kev_date_added":null,"published":"2019-04-11"},{"cvss_score":8.8,"headline":"Silverstripe CSRF Protection Bypass via GraphQL","id":"CVE-2019-12437","kev_date_added":null,"published":"2020-02-19"},{"cvss_score":7.5,"headline":"Silverstripe CMS information disclosure","id":"CVE-2020-6164","kev_date_added":null,"published":"2020-07-15"},{"cvss_score":7.5,"headline":"SilverStripe Folders migrated from 3.x may be unsafe to upload to","id":"CVE-2020-9280","kev_date_added":null,"published":"2020-04-15"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2011-4960","kev_date_added":null,"published":"2012-09-17"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"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":"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":"Attackers can bypass form validation by using square brackets in field names, potentially submitting invalid or malicious data.","url":"https://insights.sbomify.com/CVE-2020-26138/"}