# DRUPAL-CONTRIB-2019-062: This module improves the Drupal login page with the new features and layout.

> An authenticated administrator can inject malicious scripts into login page text fields, potentially leading to code execution or security bypass.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Aug 2019

## What is DRUPAL-CONTRIB-2019-062?

DRUPAL-CONTRIB-2019-062 is a cross-site scripting vulnerability in drupal/super_login, published on 14 Aug 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

This module improves the Drupal login page with the new features and layout.

The module doesn't sufficiently filter input text in the administration pages text configuration inputs. For example, the login text field.

The vulnerability is mitigated by the fact it can only be exploited by a user with the "Administer super login" permission.

## Which versions are affected by DRUPAL-CONTRIB-2019-062?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/super_login` | Packagist:https://packages.drupal.org/8 | All versions | 1.3.0 |

## How do I fix DRUPAL-CONTRIB-2019-062?

Upgrade to a fixed version.

## Is DRUPAL-CONTRIB-2019-062 being exploited?

There is no known exploitation of DRUPAL-CONTRIB-2019-062 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for DRUPAL-CONTRIB-2019-062 and fix it if it is affected.

What it is: DRUPAL-CONTRIB-2019-062 is a cross-site scripting vulnerability in drupal/super_login, published on 14 Aug 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of DRUPAL-CONTRIB-2019-062 in the wild and no public exploit code.

Affected product: drupal/super_login. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-062/ (Markdown: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-062/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/DRUPAL-CONTRIB-2019-062

---
From sbomify Insights: https://insights.sbomify.com/DRUPAL-CONTRIB-2019-062/
Summaries are generated and may contain mistakes; the official description above is the record.