Vulnerability in Drupal API Key manager (CVE-2025-9553)
Summary
Vulnerability in Drupal API Key manager (CVE-2025-9553). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
The security team is marking this project unsupported. There is a known security issue with the project that has not been fixed by the maintainer. If you would like to maintain this project, please read: https://www.drupal.org/node/251466#s-becoming-owner-maintainer-or-co-mai...
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A weakness called CVE-2025-9553 was discovered in Drupal API Key manager.
Severity is Medium (CVSS 5.3/10). Exploitation requires specific conditions but can cause real harm if successful.
What you should do: update the affected software to the latest version. If unsure, ask your IT team or search the vendor's site for "Drupal API Key manager CVE-2025-9553".
CVE-2025-9553 (Drupal API Key manager). Severity: Medium / CVSSv3 5.3.
Response plan:
- Check the vendor advisory for affected versions and the patched release.
- If a vulnerable version is running in production, schedule maintenance (urgency from KEV/CVSS).
- If no patch yet, mitigate via WAF rule, disabling the affected feature, etc.
- Monitor logs / SIEM for known IOC and PoC signatures of this CVE.
PoCs and fix commits: see the 'References' section, MITRE, and NVD.
A weakness (CVE-2025-9553) in Drupal API Key manager. A serious software flaw has been identified.
Target versions of Drupal API Key manager (see vendor advisory). If running in production, identify exposure immediately.
Severity: Medium (CVSS 5.3/10). Exploitation requires specific conditions but can cause real harm if successful.
Update to the patched release as listed in the vendor advisory.
If a patch is not yet available, consider disabling the affected feature, applying WAF rules, blocking via network ACLs, or isolating the vulnerable version.
Check version information, scan dependencies via SBOM, and monitor SIEM for IOC and PoC signatures related to this CVE.
Affected packages
References
- web drupal.org