VulnerabilityPublished 10 Oct 2025Updated 15 Oct 2025

CVE-2025-9554: Drupal Owl Carousel 2

Affects Drupal Owl Carousel 2Source CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 11:42 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 26 Oct 2026.

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 or the CVSS exploit maturity 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 Owl Carousel 2	Affected *	Fixed in–

AI-suggested

Given the current lack of official patches, European organizations should implement the following specific mitigations: 1) Conduct an immediate audit of Drupal installations to identify the presence and usage of Owl Carousel 2 modules. 2) Restrict public access to endpoints or resources related to Owl Carousel 2 where feasible, using web application firewalls (WAFs) or access control lists (ACLs) to limit exposure. 3) Monitor web server logs and network traffic for unusual or unauthorized access patterns targeting carousel-related URLs or resources. 4) Employ content security policies (CSP) and input validation to reduce the risk of data leakage through the carousel interface. 5) Engage with Drupal community channels and vendors to track the release of official patches or updates addressing CVE-2025-9554 and apply them promptly. 6) Consider temporary removal or disabling of the Owl Carousel 2 module if the risk outweighs its utility until a fix is available. 7) Educate web administrators and developers about the vulnerability to ensure awareness and rapid response. 8) Integrate this vulnerability into vulnerability management and incident response workflows to ensure continuous monitoring and mitigation.

Description

Vulnerability in Drupal Owl Carousel 2.This issue affects Owl Carousel 2: *.*.

Impact

For European organizations, the primary impact of CVE-2025-9554 is the potential unauthorized disclosure of sensitive information related to website content or configuration managed via the Owl Carousel 2 module. This could include internal URLs, image metadata, or other data that may facilitate further targeted attacks such as phishing, social engineering, or reconnaissance for more severe exploits. While the vulnerability does not affect data integrity or service availability, the confidentiality breach can undermine trust, expose proprietary content, or reveal infrastructure details. Organizations operating public-facing Drupal websites with Owl Carousel 2 integrated are at risk, particularly those in sectors with high data sensitivity such as government, finance, healthcare, and critical infrastructure. The medium severity rating reflects a moderate risk that can escalate if combined with other vulnerabilities. The absence of known exploits reduces immediate threat but does not eliminate the risk of future weaponization. European entities must consider the regulatory implications of data exposure under GDPR, which mandates protection of personal and sensitive data, potentially leading to compliance issues and fines if exploited.

References

drupal.org/sa-contrib-2025-104 (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:56 UTC

Technical details

References

Community reviews

Related threats