(CVE-2025-31688)
Vulnerability from drupal – Published: 2025-02-12 17:38 – Updated: 2025-03-31 22:05 – Source websiteThis module enables you to create super sets of configuration and enable them conditionally, for example have some modules installed only in some environments.
The module does not use Cross Site Request Forgery (CSRF) tokens to protect routes for enabling or disabling a split.
This vulnerability is mitigated by the fact that an attacker must know the machine name of a split and deceive a user with the permission to modify it.
The status only takes effect when exporting the configuration (1.x and 2.x) or importing the configuration (1.x only) and the status is not fixed via configuration override, which is the typical setup.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.10.0 || \u003e=2.0.0 \u003c2.0.2"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/config_split"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.10.0"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.10.0"
}
],
"type": "ECOSYSTEM"
},
{
"database_specific": {
"constraint": "\u003e=2.0.0 \u003c2.0.2"
},
"events": [
{
"introduced": "2.0.0"
},
{
"fixed": "2.0.2"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2025-31688"
],
"credits": [
{
"contact": [
"https://www.drupal.org/u/ericgsmith"
],
"name": "Eric Smith (ericgsmith)"
}
],
"details": "This module enables you to create super sets of configuration and enable them conditionally, for example have some modules installed only in some environments.\n\nThe module does not use Cross Site Request Forgery (CSRF) tokens to protect routes for enabling or disabling a split.\n\nThis vulnerability is mitigated by the fact that an attacker must know the machine name of a split and deceive a user with the permission to modify it. \nThe status only takes effect when exporting the configuration (1.x and 2.x) or importing the configuration (1.x only) and the status is not fixed via configuration override, which is the typical setup.",
"id": "DRUPAL-CONTRIB-2025-017",
"modified": "2025-03-31T22:05:40.000Z",
"published": "2025-02-12T17:38:22.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2025-017"
}
],
"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.