Open SocialDrupal extension · Getopensocial
CVE-2024-13274
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 · uneditedImproper Control of Interaction Frequency vulnerability in Drupal Open Social allows Functionality Misuse.This issue affects Open Social: from 0.0.0 before 12.3.8, from 12.4.0 before 12.4.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 · high confidenceDrupal Open Social fails to properly control interaction frequency, allowing authenticated or anonymous users to abuse functionality by performing excessive requests or actions (e.g., posting, messaging, API calls) without appropriate rate limiting, potentially leading to resource exhaustion or service degradation.
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
< 12.3.8>= 12.4.0, < 12.4.5CVSS 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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Open Social versionLocate the version file or check via composer (composer show getopensocial/social) or access the admin dashboard under Administration > Configuration > Open Social settings to view the version numberAffected if The version is less than 12.3.8, or greater than or equal to 12.4.0 but less than 12.4.5
-
Verify rate limiting configuration for user interactionsNavigate to the rate limiting or flood control settings in the Drupal/Open Social admin interface (typically under Configuration > People > Flood settings or similar) and inspect whether interaction frequency controls are enabled for posting, messaging, and API functionalityAffected if Rate limiting is disabled, not configured, or missing for the affected interaction types (posting, messaging, API calls)
-
Confirm exposed functionality is accessibleVerify that the vulnerable functionality (user posting, private messaging, API endpoints) is publicly accessible or accessible to authenticated users without rate limiting restrictionsAffected if The posting, messaging, or API functionality is enabled and accessible without any rate limiting enforcement in place
You are affected if your Open Social version is in the vulnerable range and rate limiting is not properly configured for user interactions such as posting, messaging, or API calls.
Generated from the published advisory. Verify against your own configuration.
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 · scoped12.3.812.4.5
Update Drupal Open Social to version 12.3.8 or 12.4.5 or later to receive the patched code that implements proper interaction frequency controls on the affected functionality.
Upgrade to 12.3.8 (if on 12.x branch) or 12.4.5 (if on 12.4.x branch)
- 1. Back up your Drupal database and files before updating
- 2. Update Open Social using Composer: `composer require drupal/social:^12.3.8` or `composer require drupal/social:^12.4.5` depending on your current version branch
- 3. Run Drupal database updates: `drush updatedb` or `php core/scripts/drupal update-db`
- 4. Clear Drupal caches: `drush cr` or `php core/scripts/drupal cache-clear`
- 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
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-13274 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-13274 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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