CVE-2025-9552VulnerabilityPublished 10 Oct 2025Updated 15 Oct 2025

CVE-2025-9552: Drupal Synchronize composer.json With Contrib Modules · Vulnerability

Affects Drupal Synchronize composer.json With Contrib ModulesSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Oct 2025
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 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Drupal Synchronize composer.json With Contrib Modules	Affected *	Fixed in–

AI-suggested

Organizations should immediately inventory their Drupal environments to identify installations using the 'Synchronize composer.json With Contrib Modules' module. Until an official patch is released, restrict network access to Drupal administrative interfaces and related endpoints to trusted internal IPs only. Implement strict web application firewall (WAF) rules to detect and block suspicious requests targeting composer.json synchronization functionality. Regularly monitor Drupal security advisories and community channels for patch releases or mitigation updates. Employ vulnerability scanning tools capable of detecting this specific module and its versions. Consider disabling or removing the module if it is not essential to operations. Additionally, conduct security awareness training for administrators to recognize potential exploitation attempts. For environments with high security requirements, perform manual code reviews or penetration testing focused on this module's synchronization features to identify any exploitable weaknesses.

Description

Vulnerability in Drupal Synchronize composer.Json With Contrib Modules.This issue affects Synchronize composer.Json With Contrib Modules: *.*.

Impact

For European organizations, this vulnerability poses a moderate risk primarily to the confidentiality of configuration data within Drupal environments. Exposure of composer.json synchronization details could reveal module versions, dependencies, or environment specifics that attackers might leverage for targeted attacks or privilege escalation. While the vulnerability does not directly affect integrity or availability, the information disclosure could facilitate subsequent exploitation steps. Organizations running public-facing Drupal websites or intranet portals using this module are at risk, especially if external access is unrestricted. The impact is more pronounced for entities with sensitive data or critical web services hosted on Drupal, such as government agencies, financial institutions, and large enterprises. The absence of known exploits reduces immediate risk but does not eliminate the need for proactive mitigation. Failure to address this vulnerability could lead to reconnaissance by threat actors, increasing the likelihood of more severe attacks in the future.

References

drupal.org/sa-contrib-2025-102 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 18 Oct 2025, 03:57 UTC

Technical details

References

Community reviews

Related threats