dbcve.org
Entity ShareDrupal extension · Ithom

CVE-2025-13985

MEDIUM · 5.3 CVSS v3.1 Published 2026-01-28
Fix available
A fix is available. Upgrade to 3.13.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Incorrect Authorization vulnerability in Drupal Entity Share allows Forceful Browsing.This issue affects Entity Share: from 0.0.0 before 3.13.0.

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

Incorrect authorization vulnerability in Drupal Entity Share module allows Forceful Browsing, where users can access entities or resources they should not have permission to access by directly navigating to them, bypassing proper authorization controls.

MitigationUpgrade Entity Share module to version 3.13.0 or later to remediate the authorization bypass. Verify all entity access controls function correctly after the update.

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 ShareDrupal extension
Affected:< 3.13.0

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
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify Entity Share module version
    Check the installed version of the Entity Share module in your Drupal installation. This can be done via the Drupal admin interface under Extend, or by checking the module's .info.yml file or composer.json
    Affected if the installed version is lower than 3.13.0
  2. Verify Entity Share module is enabled
    Confirm that the Entity Share module is currently enabled on your Drupal site through the module administration page
    Affected if the module is enabled and the version is below 3.13.0
  3. Review entity access permissions
    Inspect the permission configuration for Entity Share in Drupal's permissions administration. Check if entity access controls are properly configured for the content types and entities that Entity Share exposes
    Affected if users with limited permissions can access entities they should not have access to by directly navigating to entity URLs
  4. Test direct entity URL access
    Attempt to access entity resources directly via their URLs (such as JSON:API or REST endpoints exposed by Entity Share) using an account that should NOT have access to those specific entities
    Affected if unauthorized access succeeds when it should be denied, indicating the authorization bypass is present

Your environment is affected if the Entity Share module version is below 3.13.0 and the module is enabled, allowing unauthorized users to bypass access controls by directly navigating to entity URLs.

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 3.13.0 or later
Fixed in 3.13.0
Interim mitigation

Upgrade Entity Share module to version 3.13.0 or later to remediate the authorization bypass. Verify all entity access controls function correctly after the update.

Recommended fix High confidence

3.13.0

  1. Identify the Drupal installation that includes the Entity Share module
  2. Locate the composer.json file for the Drupal project
  3. Run 'composer require drupal/entity_share:^3.13.0' to update to the fixed version
  4. Run 'composer update drupal/entity_share' to apply the changes
  5. Verify the updated version by running 'composer show drupal/entity_share'
  6. Clear Drupal cache using 'drush cr' or through the admin UI at /admin/config/development/performance
  7. Verify the fix by checking that unauthorized users can no longer access entities they should not have access to via Entity Share
Caveat Review Entity Share 3.13.0 release notes for any breaking changes or deprecations before upgrading in production environments

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

Fix this in Entity Share Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13985 — 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-13985 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