VulnerabilityPublished 10 Oct 2025Updated 15 Oct 2025

CVE-2025-9553: Drupal API Key manager

Affects Drupal API Key managerSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium.

Data as of 26 Oct 2026, 09:16 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 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 API Key manager	Affected *	Fixed in–

AI-suggested

1. Immediately restrict public access to the Drupal API Key manager endpoints by implementing network-level controls such as IP whitelisting or VPN access. 2. Monitor web server and application logs for unusual or unauthorized access attempts targeting API key management functions. 3. Apply strict access control policies within Drupal to limit who can view or manage API keys, ensuring only trusted administrators have permissions. 4. Use web application firewalls (WAF) to detect and block suspicious requests that may attempt to exploit this vulnerability. 5. Regularly audit API keys stored in Drupal and rotate them to invalidate potentially exposed credentials. 6. Stay alert for official Drupal security advisories and apply patches or updates as soon as they become available. 7. Consider isolating API key management functionality from public-facing systems or using external secure vault solutions for API key storage. 8. Educate administrators on the risks of API key exposure and best practices for secure key management.

Description

Vulnerability in Drupal API Key manager.This issue affects API Key manager: *.*.

Impact

For European organizations, the primary impact is the potential exposure of API keys managed by Drupal installations, which could lead to unauthorized access to connected services or data. This may result in data leakage or unauthorized use of APIs, potentially compromising sensitive business operations or customer data. Organizations in sectors such as government, finance, healthcare, and critical infrastructure that utilize Drupal for their web presence or API management are particularly at risk. The confidentiality breach could facilitate further attacks if attackers leverage exposed API keys to pivot into internal systems or third-party services. However, since the vulnerability does not affect integrity or availability, direct service disruption or data tampering is unlikely. The absence of known exploits reduces immediate threat levels but does not eliminate the risk of future exploitation. European entities with public-facing Drupal sites using the API Key manager should consider this vulnerability a moderate risk that requires timely remediation to prevent escalation.

References

drupal.org/sa-contrib-2025-103 (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