(CVE-2026-107312)

Vulnerability from drupal – Published: 2026-10-07 16:39 – Updated: 2026-10-07 17:14 – Source website
VLAI
Details

The Examples for Developers project aims to provide high-quality, well-documented API examples for a broad range of Drupal core functionality.

The "Email Example" feature implemented by the email_example submodule can be used to send illegitimate emails to arbitrary email addresses.

Therefore, the email_example sub-module is being removed from Examples for Developers until a version demonstrating security best practices can be added back in the future. Developers who based a new module on this example should review their code.

Credits
Alberto Paderno (avpaderno) www.drupal.org/u/avpaderno
References
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003c4.0.7"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/examples"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003c4.0.7"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "4.0.7"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [
    "CVE-2026-107312"
  ],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/u/avpaderno"
      ],
      "name": "Alberto Paderno (avpaderno)"
    }
  ],
  "details": "The Examples for Developers project aims to provide high-quality, well-documented API examples for a broad range of Drupal core functionality.\n\nThe \"Email Example\" feature implemented by the email\\_example submodule can be used to send illegitimate emails to arbitrary email addresses.\n\nTherefore, the email\\_example sub-module is being removed from Examples for Developers until a version demonstrating security best practices can be added back in the future. Developers who based a new module on this example should review their code.",
  "id": "DRUPAL-CONTRIB-2026-215",
  "modified": "2026-10-07T17:14:03.000Z",
  "published": "2026-10-07T16:39:53.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2026-215"
    }
  ],
  "schema_version": "1.7.0"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

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.



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.