CVE-2026-118566: The Content Synchronizer module allows content to be exported and imported between Drupal sites via uploaded archive fil

unknown Affects drupal/content_synchronizer. Feed 2026.11.09.1, updated 2026-11-08; published 2026-11-04.

The Content Synchronizer module allows content to be exported and imported between Drupal sites via uploaded archive fil

Package: drupal/content_synchronizer Composer
Affected versions: <4.1.1
Fixed in: 4.1.1
Severity: unknown
Exploitation: not on CISA KEV
Published: 2026-11-04
Source: osv.dev

References

https://www.drupal.org/sa-contrib-2026-294

NVD record drupal/content_synchronizer advisories

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

Related advisories

CVE-2026-118547 unknown The Content Synchronizer module allows content to be exported and imported between Drupal same package: drupal/content_synchronizer
CVE-2026-109618 KEV critical Upload-progress use-after-free and remote process-memory disclosure also from 2026
CVE-2026-109619 KEV critical Fatal-error backtrace use-after-free and OPcache type confusion also from 2026
CVE-2026-9082 KEV critical Drupal core includes a database abstraction API to ensure that queries executed against th also from 2026
CVE-2026-63030 KEV critical WordPress 6.9.x before 6.9.5 and 7.0.x before 7.0.2 is affected by a REST API batch endpoi also from 2026
CVE-2026-60137 KEV medium WordPress 6.8.x before 6.8.6, 6.9.x before 6.9.5, and 7.0.x before 7.0.2 does not properly also from 2026