silverstripe/userforms file upload exposure on UserForms module

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

The userforms module 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. In 3.0.0 this field is disabled by default, but re-enabled upon installation of the secure assets module. 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. Existing file upload fields will not be disabled, but will require re-enabling via config or installation of secure assets to become editable again. If any upload field points or is pointed to a folder that is not secured, and…

Published by the source

28 May 2024, 17:21 UTC

Last modified by the source

28 May 2024, 17:21 UTC

Source last checked

26 Oct 2026, 14:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-55pp-293f-3365

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-55pp-293f-3365

Advisory: silverstripe/userforms file upload exposure on UserForms module
IDs: GHSA-55pp-293f-3365
Record: https://patchnext.com/advisories/ghsa-55pp-293f-3365 (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: silverstripe/userforms 3.0.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist silverstripe/userforms: affected < 3.0.0; fixed in 3.0.0

## Suggested inspection (read-only)
- Packagist silverstripe/userforms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on silverstripe/userforms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-55pp-293f-3365 (GitHub-reviewed advisory GHSA-55pp-293f-3365 lists affected ranges: Packagist silverstripe/userforms >=0 <3.0.0)

Commands are suggestions: review each one before running it.