Events Log TrackWordPress extension · Events Log Track Project
CVE-2025-4416
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 · uneditedAllocation of Resources Without Limits or Throttling vulnerability in Drupal Events Log Track allows Excessive Allocation.This issue affects Events Log Track: from 0.0.0 before 3.1.11, from 4.0.0 before 4.0.2.
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 · high confidenceThe Drupal Events Log Track module lacks proper resource limits or throttling, allowing excessive allocation that could enable denial of service through resource exhaustion.
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
Events Log TrackWordPress extension
< 3.1.11>= 4.0.0, < 4.0.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Events Log Track module is installedCheck your Drupal site's module directory or list installed modules via drush pm:list, or inspect the modules/events_log_track directory in your codebaseAffected if The Events Log Track module is present in the Drupal installation
-
Identify installed module versionCheck the version in the module's .info.yml file (e.g., events_log_track.info.yml) or run 'composer show drupal/events_log_track' if managed via ComposerAffected if A version number is returned that can be compared against the affected ranges
-
Compare version against affected rangesDetermine if the installed version is < 3.1.11 OR >= 4.0.0 AND < 4.0.2. For example, versions 3.1.10, 3.0.0, or 4.0.1 are affected.Affected if The installed version falls within < 3.1.11 or >= 4.0.0 and < 4.0.2
-
Verify module is enabled and processing eventsCheck if the module is enabled in Drupal (via admin/modules or drush pm:list --status=enabled) and that event logging is activeAffected if The module is enabled and actively processing log events, making the resource exhaustion flaw exploitable
A defender is affected if the Events Log Track module is installed, enabled, and running a version below 3.1.11 or between 4.0.0 and 4.0.1 inclusive.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.1.114.0.2
Update Events Log Track module to version 3.1.11 or 4.0.2 or later to receive the patch for this resource exhaustion vulnerability.
Events Log Track 3.1.11 or 4.0.2 (depending on your major version branch)
- 1. Back up your Drupal site database and files before making any changes
- 2. If using Composer, run 'composer update drupal/events_log_track --with-all-dependencies' to update to the latest version
- 3. Alternatively, download version 3.1.11 or 4.0.2 (depending on your current major version) from drupal.org/project/events_log_track
- 4. Replace the existing events_log_track module directory with the new version
- 5. Run database updates: 'drush updatedb' or via the web interface at /update.php
- 6. Clear Drupal caches: 'drush cr' or via the web interface
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Events Log Track
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4416 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-4416 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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