dbcve.org
Open SocialDrupal extension · Getopensocial

CVE-2025-31686

HIGH · 8.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 →
90/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

A missing authorization vulnerability in Drupal Open Social allows users to perform forceful browsing, accessing protected pages or resources by directly navigating to URLs without proper permission checks. This bypasses intended access controls.

MitigationUpdate Drupal Open Social to version 12.3.11 or 12.4.10 or later to obtain the fix for 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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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 installed Open Social version
    Check the version.php file in the Open Social installation directory, typically at /html/libraries/highlight/node_modules/vendor/composer/installed.json or check the Drupal system table: SELECT version FROM system WHERE name = 'social_core' AND type = 'module';
    Affected if Version is less than 12.3.11 OR (version >= 12.4.0 AND version < 12.4.10)
  2. Confirm Open Social module is enabled
    Run: drush pm-list --status=enabled --type=module | grep social OR check the Drupal modules table: SELECT name FROM system WHERE name LIKE 'social_%' AND status = 1;
    Affected if At least one social_* module is enabled and version is in the affected range
  3. Identify protected routes that should require authorization
    Review the Drupal routing configuration for routes defined in social_core, social_group, or social_profile modules. Check /html/web/modules/custom/social_core/social_core.routing.yml or run: drush route-list --format=yaml
    Affected if Routes with _permission or _role requirements exist and the version is vulnerable
  4. Test for forceful browsing on protected pages
    Attempt to access a protected page directly via URL without authentication or with a low-privilege user account. For example, navigate to /admin/content, /group, or /user/*/profile without proper session tokens.
    Affected if Access is granted when it should be denied, indicating the authorization check is missing

A user is affected if Open Social version is less than 12.3.11 or between 12.4.0 and 12.4.10 (exclusive), and forceful browsing to protected routes is possible without proper authorization.

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 obtain the fix for the missing authorization check.

Recommended fix High confidence

Open Social 12.3.11 or 12.4.10 (depending on your current major version branch)

  1. 1. Back up your Drupal database and codebase before proceeding
  2. 2. Update Open Social using Composer: run `composer require drupal/social:^12.3.11` (for 12.x versions) or `composer require drupal/social:^12.4.10` (for 12.4.x versions)
  3. 3. Alternatively, update via Drupal admin UI at /admin/modules/update or using Drush: `drush up drupal/social`
  4. 4. Run database updates: `drush updb` or via admin UI at /update.php
  5. 5. Clear Drupal caches: `drush cr` or via admin UI at /admin/config/development/performance
Caveat Review Open Social release notes for any configuration or API changes between your current version and the target version before upgrading

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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