dbcve.org
Open SocialDrupal extension · Getopensocial

CVE-2024-13241

CRITICAL · 9.1 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 12.0.5 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
Improper Authorization vulnerability in Drupal Open Social allows Collect Data from Common Resource Locations.This issue affects Open Social: from 0.0.0 before 12.0.5.

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

Improper Authorization vulnerability in Drupal Open Social allows unauthorized users to collect data from common resource locations due to missing authorization checks on certain endpoints. This allows attackers to access sensitive data they should not have permission to view.

MitigationUpgrade to Open Social version 12.0.5 or later which contains proper authorization controls for resource location endpoints.

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.0.5

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

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

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

  1. Identify Open Social version
    Check your Drupal installation for the installed Open Social version. This can be found in the Drupal admin interface under Configuration > System > Simple XML sitemap, or by checking the composer.json file in your Open Social installation directory for the 'drupal/social' package version.
    Affected if The installed version is lower than 12.0.5 (e.g., 12.0.4, 12.0.3, 11.x, etc.)
  2. Verify endpoint accessibility
    Review your web server logs and access logs for requests to common resource location endpoints (e.g., API endpoints, data export endpoints, resource files). Use network logging tools or review access logs to identify which endpoints are accessible.
    Affected if Endpoints that should require authentication are responding to unauthenticated or unauthorized users
  3. Check user role permissions
    Navigate to Drupal administration > People > Permissions. Review whether the anonymous user role or unauthenticated users have been granted access to resource endpoints, data export features, or API endpoints that should be restricted.
    Affected if Unauthenticated or unauthorized user roles have access to sensitive resource endpoints that should be protected
  4. Inspect API and resource endpoints
    Test access to common resource endpoints using an unauthenticated browser session or a non-privileged user account. Attempt to access endpoints that expose data, such as user profile data, content listings, or exported resources.
    Affected if Sensitive data or resource endpoints are accessible without proper authentication or authorization
  5. Review endpoint configuration
    Check the Open Social configuration at /admin/config/social to identify enabled features and endpoints. Look for any resource location or data export features that may be exposed.
    Affected if Resource location endpoints or data export features are enabled and accessible to unauthorized users

A user is affected if their Open Social installation is version 12.0.5 or higher and endpoints are properly restricted, or if they are running a version below 12.0.5 with accessible unprotected resource endpoints.

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.0.5 or later
Fixed in 12.0.5
Interim mitigation

Upgrade to Open Social version 12.0.5 or later which contains proper authorization controls for resource location endpoints.

Recommended fix High confidence

12.0.5

  1. Create a full backup of the database and codebase before proceeding
  2. Update Open Social using Composer: run `composer require drupal/social:^12.0.5` or `composer update drupal/social --with-all-dependencies`
  3. Run database updates via `drush updatedb` or through the web interface at /update.php
  4. Clear all caches using `drush cr` or through the Drupal admin interface
  5. Verify the installation is functioning correctly after the update
Caveat Review release notes for any breaking changes between your current version and 12.0.5; test in a staging environment first

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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