CVE intelligence and bounded remediation

CVE-2025-12848 — Webform Multiple File Upload module for Drupal 7.x contains a cross-site scripting (XSS) vulnerability in the file name renderer

High CVSS 7

Webform Multiple File Upload module for Drupal 7.x contains a cross-site scripting (XSS) vulnerability in the file name renderer. An unauthenticated attacker can exploit this vulnerability by uploading a file with a malicious filename containing JavaScript code (e.g., "<img src=1 onerror=alert(document.domain)>") to a Webform node with a Multifile field where file type validation is disabled. This allows the execution of arbitrary scripts in the context of the victim's browser. The issue is present in a third-party library and has been addressed in a patch available at https://github.com/fyneworks/multifile/pull/44 . Users are advised to apply the provided patch or update to a fixed version of the module.

Severity
High
CVSS
7 (4.0)
Published
2025-11-26
CISA KEV
Not currently listed
Ecosystem
javascript/npm
Weaknesses
CWE-79

Affected products

  • webform_multiple_file_upload_project / webform_multiple_file_upload / 7.x-1.2
  • webform_multiple_file_upload_project / webform_multiple_file_upload / 7.x-1.3
  • webform_multiple_file_upload_project / webform_multiple_file_upload / 7.x-1.4
  • webform_multiple_file_upload_project / webform_multiple_file_upload / 7.x-1.5
  • webform_multiple_file_upload_project / webform_multiple_file_upload / 7.x-1.6
  • webform_multiple_file_upload_project / webform_multiple_file_upload / 7.x-1.x

Matched remediation archetype

Cross-site scripting and unsafe browser output

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Trace reflected, stored, and DOM-derived untrusted values into HTML, attributes, URLs, styles, scripts, and client-side template sinks.
  • Identify affected origins, authenticated user roles, sensitive browser capabilities, and where content is shared across tenants.
  • Review framework escaping, rich-text sanitization, legacy templates, and client-side rendering paths.

Remediate safely

  • Use context-aware framework output encoding and safe DOM APIs; keep untrusted data out of executable contexts.
  • Sanitize intentionally supported markup with a maintained allowlist policy and validate URLs and attributes separately.
  • Update affected rendering components and add tests for every output context using inert sentinel markup.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.