{"answers":{"affected":"2 open source packages ship an affected version, including silverstripe/userforms.","exploited":"There is no known exploitation of GHSA-55pp-293f-3365 in the wild and no public exploit code.","fix":"Upgrade silverstripe/userforms to 3.0.0 or later.","what":"GHSA-55pp-293f-3365 is a vulnerability in silverstripe/userforms, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-55pp-293f-3365 and fix it if it is affected.\n\nWhat it is: GHSA-55pp-293f-3365 is a vulnerability in silverstripe/userforms, published on 28 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-55pp-293f-3365 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- silverstripe/userforms (Packagist): affected all versions; fixed in 3.0.0\n- silverstripe/userforms (Packagist): affected all versions; fixed in 3.0.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/GHSA-55pp-293f-3365/ (Markdown: https://insights.sbomify.com/GHSA-55pp-293f-3365/index.md)","id":"GHSA-55pp-293f-3365","markdown":"https://insights.sbomify.com/GHSA-55pp-293f-3365/index.md","name":"GHSA-55pp-293f-3365","record":{"aliases":[],"analysis":{"component_type":"cms_plugin","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"SilverStripe UserForms plugin","requires_auth":"none","summary":"Attackers can access uploaded form files via predictable paths or exposed links in notification emails, leading to data disclosure.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"The [userforms module](https://github.com/silverstripe/silverstripe-userforms) allows CMS administrators to create public facing forms with file upload abilities. These files are uploaded into a predictable public path on the website, unless configured otherwise by the CMS administrator setting up the form. While the name of the uploaded file itself is not predictable, certain actions taken by CMS authors could expose it. For example, submission notification emails contain a link to the file without authorisation checks.\n\nIn 3.0.0 this field is disabled by default, but re-enabled upon installation of the [secure assets module](https://github.com/silverstripe-labs/silverstripe-secureassets). When this is installed, the field can once again be used within a form, and will automatically lock this folder to a secure list of users, which can then be configured further by an administrator.\n\nExisting file upload fields will not be disabled, but will require re-enabling via config or installation of secure assets to become editable again.\n\nIf any upload field points or is pointed to a folder that is not secured, and the secure assets module is present, then that folder will have the secure permissions applied automatically.","ecosystems":["Packagist"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"silverstripe/userforms file upload exposure on UserForms module","id":"GHSA-55pp-293f-3365","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Packagist","product":null,"products":[],"type":"information_disclosure","year":"2024"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Packagist","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"silverstripe/userforms","purl":null,"source":"GHSA-55pp-293f-3365"},{"ecosystem":"Packagist","fixed":["3.0.0"],"introduced":["0"],"last_affected":[],"package":"silverstripe/userforms","purl":"pkg:composer/silverstripe/userforms","source":"GHSA-55pp-293f-3365"}],"products":null,"published":"2024-05-28","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Attackers can access uploaded form files via predictable paths or exposed links in notification emails, leading to data disclosure.","url":"https://insights.sbomify.com/GHSA-55pp-293f-3365/"}