(CVE-2026-118555)
Vulnerability from drupal – Published: 2026-10-28 16:56 – Updated: 2026-10-28 16:56 – Source websiteThis module enables you to sell licenses granting access to resources, such as user roles, files, or protected content.
The module doesn't sufficiently restrict access to license fields for users with the "update own commerce_license" permission. A license owner can change the rights granted by their license and the license state, which can result in privilege escalation, up to the Administrator role for the site.
This vulnerability is mitigated by the fact that an attacker must own a license, and have a role with the "update own commerce_license" permission, which is not granted by default.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c3.1.1"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/commerce_license"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c3.1.1"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "3.1.1"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2026-118555"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/marcus_johansson"
],
"name": "Marcus Johansson (marcus_johansson)"
}
],
"details": "This module enables you to sell licenses granting access to resources, such as user roles, files, or protected content.\n\nThe module doesn\u0027t sufficiently restrict access to license fields for users with the \"update own commerce\\_license\" permission. A license owner can change the rights granted by their license and the license state, which can result in privilege escalation, up to the Administrator role for the site.\n\nThis vulnerability is mitigated by the fact that an attacker must own a license, and have a role with the \"update own commerce\\_license\" permission, which is not granted by default.",
"id": "DRUPAL-CONTRIB-2026-260",
"modified": "2026-10-28T16:56:16.000Z",
"published": "2026-10-28T16:56:16.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2026-260"
}
],
"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.