dbcve.org
Admin Audit TrailDrupal extension · Admin Audit Trail Project

CVE-2025-48448

MEDIUM · 6.5 CVSS v3.1 Published 2025-06-11
Fix available
A fix is available. Upgrade to 1.0.5 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Allocation of Resources Without Limits or Throttling vulnerability in Drupal Admin Audit Trail allows Excessive Allocation.This issue affects Admin Audit Trail: from 0.0.0 before 1.0.5.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Admin Audit Trail module for Drupal lacks proper resource limits or throttling on audit log entries, allowing an attacker to trigger excessive allocation of system resources (memory, storage, or CPU) by generating large volumes of audit events. This can lead to denial of service through resource exhaustion.

MitigationUpgrade Admin Audit Trail module to version 1.0.5 or later. If immediate upgrading is not feasible, implement request rate limiting at the web server or application level to restrict the frequency of actions that generate audit trail entries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Admin Audit TrailDrupal extension
Affected:< 1.0.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Admin Audit Trail module is installed
    Run 'drush pm-list --type=module' to list installed modules, or check the modules directory for the admin_audit_trail directory. In the Drupal admin interface, navigate to Extend to see installed modules.
    Affected if The Admin Audit Trail module appears in the list of installed modules.
  2. Identify the installed version of Admin Audit Trail
    Run 'drush pm:info admin_audit_trail' to retrieve module version information, or locate the admin_audit_trail.info.yml file in the module directory and read the 'version:' or 'core_version_requirement:' field.
    Affected if The version number returned is lower than 1.0.5 (for example, 1.0.4, 1.0.3, or any 1.x version below 1.0.5).
  3. Verify the module is enabled and actively logging
    Check the module status via 'drush state:get admin_audit_trail.status' or examine the Drupal configuration at /admin/config/system/admin-audit-trail-settings. Also check the database table that stores audit logs (typically audit_log or similar) to confirm events are being recorded.
    Affected if The module is enabled and audit events are being stored in the database, meaning the resource exhaustion condition can be triggered.
  4. Check for high volume of audit log entries
    Query the audit log database table for recent entries using 'SELECT COUNT(*) FROM audit_log WHERE timestamp > UNIX_TIMESTAMP(DATE_SUB(NOW(), INTERVAL 1 HOUR));' or similar, depending on your table name. Monitor if the volume of entries correlates with high resource usage.
    Affected if A large and rapidly growing number of audit log entries is observed, indicating the module is actively logging and could be exploited.

You are affected if the Admin Audit Trail module is installed, enabled, and running with a version lower than 1.0.5, allowing an attacker to flood the system with audit events and exhaust resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.5 or later
Fixed in 1.0.5
Interim mitigation

Upgrade Admin Audit Trail module to version 1.0.5 or later. If immediate upgrading is not feasible, implement request rate limiting at the web server or application level to restrict the frequency of actions that generate audit trail entries.

Recommended fix High confidence

1.0.5

  1. Confirm the currently installed version of the Admin Audit Trail module in your Drupal installation
  2. Backup your Drupal database and files before proceeding
  3. Download Admin Audit Trail version 1.0.5 from Drupal.org (https://www.drupal.org/project/admin_audit_trail)
  4. Install the module by replacing the existing admin_audit_trail module directory with the new version
  5. Run Drupal database updates (drush updb or via the web UI at /update.php)
  6. Clear the Drupal cache (drush cr)
  7. Verify the module is now running at version 1.0.5 on the Extend administration page
  8. Test that audit trail functionality is working correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Admin Audit Trail Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48448 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48448 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data