CVE-2026-118568: Cms content sync · This module enables you to share and reuse content across websites
Affects drupal/cms_content_syncSource GCVE Database
Not known to be exploited : upgrade to 3.2.2 when convenient.
Data as of 28 Oct 2026, 20:30 UTC
Rated Medium by Threat Radar's AI analysis · CVSS not yet scored by NVD
- Patch
- Available – fixed in 3.2.2
Exploitation evidence
Disclosed: evidence found.
CVE published 28 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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/cms_content_sync to 3.2.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Packagist https //packages.drupal.org/8drupal/cms_content_sync | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the cms_content_sync module to version 3.2.2 or later, where the password encryption issue is fixed. Since the vulnerability requires prior database access, securing database access controls and monitoring for unauthorized access are also important complementary measures.
Description
The Drupal cms_content_sync module prior to version 3.2.2 insufficiently encrypted the password of the system user used for content synchronization across websites. This flaw could allow unprivileged users to view the password if they have database read access or a database dump. Exploitation requires prior access to the database, limiting the vulnerability's impact.