(CVE-2024-13271)
Vulnerability from drupal – Published: 2024-09-04 15:40 – Updated: 2025-02-20 19:23 – Source websiteThis module enables you to "clone" a content entity, i.e. to create a new content pre-filled with data from another entity of the same type and bundle.
The module doesn't properly check the user access to the original entity, allowing users to create a new entity (they have permission to create) pre-filled with content from another entity of the same type and bundle that they would normally not have access to.
This vulnerability is mitigated by the fact that an attacker must have the permission to create content of the type of the entity to clone.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"database_specific": {
"affected_versions": "\u003c1.0.4"
},
"package": {
"ecosystem": "Packagist:https://packages.drupal.org/8",
"name": "drupal/content_entity_clone"
},
"ranges": [
{
"database_specific": {
"constraint": "\u003c1.0.4"
},
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.4"
}
],
"type": "ECOSYSTEM"
}
],
"severity": []
}
],
"aliases": [
"CVE-2024-13271"
],
"credits": [
{
"contact": [
"https://www.drupal.org/user/92189"
],
"name": "Vojislav Jovanovic"
}
],
"details": "This module enables you to \"clone\" a content entity, i.e. to create a new content pre-filled with data from another entity of the same type and bundle.\n\nThe module doesn\u0027t properly check the user access to the original entity, allowing users to create a new entity (they have permission to create) pre-filled with content from another entity of the same type and bundle that they would normally not have access to.\n\nThis vulnerability is mitigated by the fact that an attacker must have the permission to create content of the type of the entity to clone.",
"id": "DRUPAL-CONTRIB-2024-035",
"modified": "2025-02-20T19:23:27.000Z",
"published": "2024-09-04T15:40:44.000Z",
"references": [
{
"type": "WEB",
"url": "https://www.drupal.org/sa-contrib-2024-035"
}
],
"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.