Entity Delete LogDrupal extension · Entity Delete Log Project
CVE-2024-13243
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 · uneditedMissing Authorization vulnerability in Drupal Entity Delete Log allows Forceful Browsing.This issue affects Entity Delete Log: from 0.0.0 before 1.1.1.
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 confidenceMissing authorization vulnerability in Drupal's Entity Delete Log module allows authenticated users to bypass access controls and access deletion log functionality they shouldn't have permission to view (forceful browsing). The module failed to properly enforce permission checks before revealing sensitive entity deletion records.
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
Entity Delete LogDrupal extension
< 1.1.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Entity Delete Log module is installedIn Drupal admin, navigate to Extend or use drush pm-list --status=enabled | grep entity_delete_log to list enabled modulesAffected if Entity Delete Log module appears in the list of enabled modules
-
Determine installed version of Entity Delete LogCheck the module's info.yml file in modules/contrib/entity_delete_log/entity_delete_log.info.yml or run: drush pm:list --field=entity_delete_log versionAffected if Version is less than 1.1.1 or the version cannot be determined (module predates proper versioning)
-
Confirm module is accessible to authenticated usersNavigate to the deletion log page path (typically /admin/config/entity-delete-log or similar) while logged in as a low-privilege authenticated user accountAffected if The page loads without a permission denied error for a user without admin roles
-
Review access logs for entity delete log pathsCheck Drupal access log tables (watchdog or access_log) for requests to entity_delete_log paths from user accounts that should not have deletion log permissionsAffected if Any GET or POST requests to deletion log paths appear for non-administrator accounts
User is affected if Entity Delete Log module version is below 1.1.1 and low-privilege authenticated users can access deletion log pages or records.
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 · scoped1.1.1
Update Entity Delete Log module to version 1.1.1 or later which includes proper authorization checks. Review user permissions and access logs for any suspicious activity occurring before the update.
1.1.1
- Backup your Drupal site database and files
- Update the Entity Delete Log module to version 1.1.1 via Composer (composer update drupal/entity_delete_log) or Drupal's admin interface
- Run database updates if prompted (drush updatedb or via admin UI)
- Clear Drupal caches (drush cr or via admin UI)
- Verify the module is updated to 1.1.1 at admin/modules
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Entity Delete Log
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13243 — 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-2024-13243 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