dbcve.org
Open SocialDrupal extension · Getopensocial

CVE-2025-31685

CRITICAL · 9.1 CVSS v3.1 Published 2025-03-31
Fix available
A fix is available. Upgrade to 12.3.11 / 12.4.10 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in Drupal Open Social allows Forceful Browsing.This issue affects Open Social: from 0.0.0 before 12.3.11, from 12.4.0 before 12.4.10.

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

This is a Missing Authorization vulnerability in Drupal Open Social that allows Forceful Browsing, where an authenticated or unauthenticated user can access resources or pages they are not authorized to access due to insufficient access control checks.

MitigationUpdate Drupal Open Social to version 12.3.11 or 12.4.10 or later to patch the missing authorization check.

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
Open SocialDrupal extension
Affected:< 12.3.11>= 12.4.0, < 12.4.10

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 checks

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

  1. Identify Open Social installation
    Check the version of Drupal Open Social installed. This is typically found in the composer.json file, or by querying the package manager (composer show opensocial/core), or checking the Drupal administration dashboard under /admin/reports/status
    Affected if The Open Social version is less than 12.3.11, or greater than or equal to 12.4.0 but less than 12.4.10
  2. Confirm Drupal core version
    Verify the Drupal core version running underneath Open Social. Check /admin/reports/status on the Drupal site, or look at the composer.lock file for the drupal/core version
    Affected if Running Drupal with Open Social versions in the affected range as identified in step 1
  3. Review access control configuration
    Examine the site configuration for any custom or overridden access control modules that might interact with Open Social's content visibility settings. Check /admin/config/people/permissions and review any custom modules in /modules/custom/
    Affected if Custom modules or configurations exist that may bypass or alter standard Open Social access checks, especially on affected versions

The environment is affected if the installed Open Social version falls below 12.3.11 or is between 12.4.0 and 12.4.10 (exclusive), as these versions contain the missing authorization check that allows forceful browsing.

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 12.3.11 / 12.4.10 or later
Fixed in 12.3.1112.4.10
Interim mitigation

Update Drupal Open Social to version 12.3.11 or 12.4.10 or later to patch the missing authorization check.

Recommended fix High confidence

Upgrade to Open Social 12.3.11 or later, OR 12.4.10 or later (depending on your current branch)

  1. 1. Backup your Drupal site database and files before proceeding with any updates.
  2. 2. Update the Open Social module using Composer: run `composer update drupal/social --with-all-dependencies` to get the latest secure version.
  3. 3. Alternatively, if using the Drupal admin interface, navigate to Extend > Update > check for updates and install the security update.
  4. 4. After updating, clear Drupal caches by running `drush cr` or via the admin interface at Configuration > Development > Performance > Clear all caches.
  5. 5. Verify the update was successful by checking the Open Social version at admin/modules or by running `drush pm:list --type=module --status=enabled | grep social`.
Caveat Security patch release; review release notes for any minor behavioral changes

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

Fix this in Open Social Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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