dbcve.org
Open SocialDrupal extension · Getopensocial

CVE-2025-48921

HIGH · 8.8 CVSS v3.1 Published 2025-06-26
Fix available
A fix is available. Upgrade to 12.3.14 / 12.4.13 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in Drupal Open Social allows Cross Site Request Forgery.This issue affects Open Social: from 0.0.0 before 12.3.14, from 12.4.0 before 12.4.13.

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 confidence

Cross-Site Request Forgery (CSRF) vulnerability in Drupal Open Social allows remote attackers to trick authenticated users into unknowingly executing unwanted actions on the application. The vulnerability exists due to missing or improper CSRF token validation on certain form submissions or state-changing operations.

MitigationUpdate Drupal Open Social to version 12.3.14 or 12.4.13 (depending on your current branch) to incorporate the security patch that adds proper CSRF token validation.

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.14>= 12.4.0, < 12.4.13

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the installed Open Social version
    Check the version number in your Drupal installation. This is typically visible in the Drupal admin dashboard under Administration > Reports > Status report, or can be found in the composer.json file in the webroot. Look for the 'social' or 'opensocial' package version.
    Affected if The installed version is less than 12.3.14, or greater than or equal to 12.4.0 but less than 12.4.13.
  2. Verify SameSite cookie attribute configuration
    Inspect your site's cookie configuration. In Drupal, this is typically set in settings.php or through the TYPO3 configuration. Check for the 'session.cookie_samesite' setting or equivalent. You can also inspect Set-Cookie headers in browser developer tools when logged into the site.
    Affected if SameSite cookie attributes are not set to 'Lax' or 'Strict', leaving the session vulnerable to cross-site requests.
  3. Confirm CSRF token validation is active
    Check if Drupal's built-in CSRF protection is functioning. This can be verified by examining form submissions in your installation - forms should include a CSRF token (form_token) that gets validated on submission. Review the Drupal logs for any CSRF validation failures.
    Affected if CSRF token validation is disabled or bypassed in your configuration.
  4. Review enabled modules that may be affected
    Check which Open Social modules are enabled in your installation. The CSRF vulnerability may affect specific functionality. List enabled modules via drush pm-list or through Administration > Extend.
    Affected if Modules related to user actions, forms, or interactive features are enabled without corresponding CSRF protections.

Your environment is affected if the installed Open Social version falls within the vulnerable ranges (< 12.3.14 or >= 12.4.0 to < 12.4.13) and SameSite cookie protection is not properly configured.

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.14 / 12.4.13 or later
Fixed in 12.3.1412.4.13
Interim mitigation

Update Drupal Open Social to version 12.3.14 or 12.4.13 (depending on your current branch) to incorporate the security patch that adds proper CSRF token validation.

Recommended fix High confidence

12.3.14 or 12.4.13 (or later respective releases)

  1. 1. Create a complete backup of your Open Social database and files
  2. 2. Update Open Social to version 12.3.14 or higher (for 12.3.x users), or version 12.4.13 or higher (for 12.4.x users)
  3. 3. Run database updates if required (drush updatedb or via web interface)
  4. 4. Clear all caches (drush cr)
  5. 5. Verify the update was successful by checking the Open Social version at /admin/reports/status

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 / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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