Categories
CVE-2025-8093 high CVSS 8.8

Vulnerability in Drupal Authenticator Login (CVE-2025-8093)

Summary

Vulnerability in Drupal Authenticator Login (CVE-2025-8093). Successful exploitation can lead to full system takeover.

Original description

The description as published by the source.

This module allows users to setup two-factor authentication (2FA) using authenticator apps for enhanced login security.

The module did not protect all possible login paths provided by core modules.

CVSS risk score (experimental) 6.3 / Medium

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

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 vulnerability tracked as CVE-2025-8093 has been found in Drupal Authenticator Login.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Drupal Authenticator Login CVE-2025-8093" on the vendor's site.

CVE-2025-8093 (Drupal Authenticator Login) — CWE-288 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-288) exists in Drupal Authenticator Login.

📍 Affected scope

Check the vendor advisory for the affected versions of Drupal Authenticator Login.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Drupal Authenticator Login を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist:https://packages.drupal.org/8 drupal/alogin
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.1.8"}],"database_specific":{"constraint":"<2.1.8"}}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details