(CVE-2026-118583)
Vulnerability from drupal – Published: 2026-10-28 17:41 – Updated: 2026-10-28 17:41 – Source websiteThis module enables you to set field-level permissions to create, update or view individual fields.
The module does not sufficiently verify administrative privileges when checking access to protected fields, potentially allowing users with a role named administrator to bypass field-level access restrictions and gain unauthorized view and edit access to protected fields.
This vulnerability is mitigated by the fact that an attacker must have a role with the machine name administrator that is not flagged as the site's administrator role. Sites that use Drupal's default administrator role configuration are not affected.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.6.0"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/field_permissions"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.6.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.6.0"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-118583"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/narbehm"
],
"name": "narbehm"
}
],
"details": "This module enables you to set field-level permissions to create, update or view individual fields.\n\nThe module does not sufficiently verify administrative privileges when checking access to protected fields, potentially allowing users with a role named `administrator` to bypass field-level access restrictions and gain unauthorized view and edit access to protected fields.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the machine name `administrator` that is not flagged as the site\u0027s administrator role. Sites that use Drupal\u0027s default administrator role configuration are not affected.",
"id": "DRUPAL-CONTRIB-2026-288",
"modified": "2026-10-28T17:41:52.000Z",
"published": "2026-10-28T17:41:52.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-288"
}
],
"schema_version": "1.7.0"
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
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.