Skip to main content
VulnerabilityPublished

CVE-2026-118561: drupal/single_content_sync · Single Content Sync enables exporting and importing content, referenced entities, and files between

Affects drupal/single_content_syncSource GCVE Database

0

Not known to be exploited : upgrade to 1.4.19 soon.

Data as of 28 Oct 2026, 20:42 UTC

Severity
High

Rated High by Threat Radar's AI analysis · CVSS not yet scored by NVD

Patch
Available – fixed in 1.4.19

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade drupal/single_content_sync to 1.4.19.

Affected software

ProductAffectedFixed in
Packagist https //packages.drupal.org/8drupal/single_content_syncAffected
  • <1.4.19
Fixed in
  • 1.4.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade the Single Content Sync module to version 1.4.19 or later, where this vulnerability is fixed. Additionally, ensure that the 'import single content' permission is restricted and granted only to trusted users, as exploitation requires this permission. Review server configurations to limit execution of attacker-controlled files to reduce risk of remote code execution.

Description

The Single Content Sync module for Drupal allows exporting and importing content, referenced entities, and files between Drupal sites. A vulnerability exists due to insufficient validation of file sources and destinations during content imports, which can enable an attacker with the import permission to write arbitrary files, disclose sensitive files accessible to the web server, or cause the server to make requests to internal or external resources. This may lead to remote code execution depending on server configuration and permissions. The import single content permission is required for exploitation and is restricted starting with version 1.4.18. The issue is fixed in version 1.4.19.

References

Community reviews

Loading reviews…