Vulnerability from drupal
Published
2026-03-04 18:02
Modified
2026-03-04 18:02
Summary
Details
This module enables you to use an external OpenID Connect login provider to authenticate and log in users on your site. If a user signs in with a login provider for the first time on the website, a new Drupal user will be created.
The module doesn't sufficiently validate the uniqueness of certain user fields depending on the database engine and its collation.
As a result, a user may be able to register with the same email address as another user.
This may lead to data integrity issues.
Credits
Eric Smith (ericgsmith)
www.drupal.org/u/ericgsmith
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.5.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/openid_connect"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.5.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.5.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-3532"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/ericgsmith"
],
"name": "Eric Smith (ericgsmith)"
}
],
"details": "This module enables you to use an external OpenID Connect login provider to authenticate and log in users on your site. If a user signs in with a login provider for the first time on the website, a new Drupal user will be created.\n\nThe module doesn\u0027t sufficiently validate the uniqueness of certain user fields depending on the database engine and its collation.\n\nAs a result, a user may be able to register with the same email address as another user.\n\nThis may lead to data integrity issues.",
"id": "DRUPAL-CONTRIB-2026-027",
"modified": "2026-03-04T18:02:59.000Z",
"published": "2026-03-04T18:02:59.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-027"
}
],
"schema_version": "1.7.0"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
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.
Loading…
Loading…