XSS attacks and security scan via testbot

Created on 1 May 2010, about 15 years ago
Updated 16 May 2025, 23 days ago

Recent patches for Form API, Filter module, and whatnot made me worry about D7's healthiness with regard to sanitation of user input on output.

The idea:

1) Enable all modules.

2) Grant all permissions.

3) Take menu router, fetch all router items having 'page callback' => 'drupal_get_form'.

4) Get all of those forms and insert <script>alert('XSS');</script> into all textfields and textareas. Submit.

5) Handle validation errors somehow. (Magic xpath trickery, but possible.)

6) Afterwards, fetch the menu router again, and visit any possible page in Drupal.

7) On every single page, assert that <script>alert('XSS');</script> is not contained in the raw output.

Feature request
Status

Needs work

Version

11.0 🔥

Component

base system

Created by

🇩🇪Germany sun Karlsruhe

Live updates comments and jobs are added and updated live.
  • Security improvements

    It makes Drupal less vulnerable to abuse or misuse. Note, this is the preferred tag, though the Security tag has a large body of issues tagged to it. Do NOT publicly disclose security vulnerabilities; contact the security team instead. Anyone (whether security team or not) can apply this tag to security improvements that do not directly present a vulnerability e.g. hardening an API to add filtering to reduce a common mistake in contributed modules.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • First commit to issue fork.
Production build 0.71.5 2024