Vulnerability from drupal
Published
2025-05-14 18:05
Modified
2025-05-14 18:05
Summary
Details

This module enables you to seamlessly migrate and deploy content across environments, eliminating manual steps. It simplifies the process by exporting content to a YML file or a ZIP archive, which can be imported into another environment effortlessly.

While the export feature rightfully bypasses implemented access controls, enabling it to extract all entity data, including private and confidential information, to the mentioned formats, it fails to adequately safeguard the generated output.

This vulnerability is mitigated by the fact that an attacker must have a role with the permission "export single content" or "Allow user to export all content".

Credits
Dezső Biczó (mxr576) www.drupal.org/u/mxr576

{
  "affected": [
    {
      "database_specific": {
        "affected_versions": "\u003c1.4.12"
      },
      "package": {
        "ecosystem": "Packagist:https://packages.drupal.org/8",
        "name": "drupal/single_content_sync"
      },
      "ranges": [
        {
          "database_specific": {
            "constraint": "\u003c1.4.12"
          },
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.4.12"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "severity": []
    }
  ],
  "aliases": [
    "CVE-2025-48009"
  ],
  "credits": [
    {
      "contact": [
        "https://www.drupal.org/u/mxr576"
      ],
      "name": "Dezs\u0151 Bicz\u00f3 (mxr576)"
    }
  ],
  "details": "This module enables you to seamlessly migrate and deploy content across environments, eliminating manual steps. It simplifies the process by exporting content to a YML file or a ZIP archive, which can be imported into another environment effortlessly.\n\nWhile the export feature rightfully bypasses implemented access controls, enabling it to extract all entity data, including private and confidential information, to the mentioned formats, it fails to adequately safeguard the generated output.\n\nThis vulnerability is mitigated by the fact that an attacker must have a role with the permission \"export single content\" or \"Allow user to export all content\".",
  "id": "DRUPAL-CONTRIB-2025-060",
  "modified": "2025-05-14T18:05:04.000Z",
  "published": "2025-05-14T18:05:04.000Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://www.drupal.org/sa-contrib-2025-060"
    }
  ],
  "schema_version": "1.7.0"
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

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…

Detection rules are retrieved from Rulezet.

Loading…

Loading…