Vulnerability from drupal
This module enables you to log the emails sent by Mailer Plus as content entities, so they can be reviewed at Reports > Mail log.
The module doesn't sufficiently redact the content of the emails it logs. Account related emails are stored with their one-time login links intact, so any user who can view the log can obtain a one-time login link for any account, including user 1, and use it to log in as that account.
This vulnerability is mitigated by the fact that an attacker must have a role with the permission View Drupal Symfony Mailer log entries, which in earlier releases was not marked as a restricted permission.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.2.7"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/symfony_mailer_log"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.2.7"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.2.7"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-16648"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/svendecabooter"
],
"name": "Sven Decabooter (svendecabooter)"
}
],
"details": "This module enables you to log the emails sent by Mailer Plus as content entities, so they can be reviewed at Reports \u003e Mail log.\n\nThe module doesn\u0027t sufficiently redact the content of the emails it logs. Account related emails are stored with their one-time login links intact, so any user who can view the log can obtain a one-time login link for any account, including user 1, and use it to log in as that account.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the permission `View Drupal Symfony Mailer log entries`, which in earlier releases was not marked as a restricted permission.",
"id": "DRUPAL-CONTRIB-2026-128",
"modified": "2026-09-02T16:34:17.000Z",
"published": "2026-09-02T16:34:17.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-128"
}
],
"schema_version": "1.7.0"
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.