dbcve.org
Ohdear IntegrationDrupal extension · Ohdear

CVE-2024-13290

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 2.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Incorrect Authorization vulnerability in Drupal OhDear Integration allows Forceful Browsing.This issue affects OhDear Integration: from 0.0.0 before 2.0.4.

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

The Drupal OhDear Integration module versions before 2.0.4 contain an incorrect authorization vulnerability that allows forceful browsing. This broken access control permits users to access protected pages or resources they should not have permission to view.

MitigationUpdate the OhDear Integration module to version 2.0.4 or later to remediate the authorization bypass. Review user role permissions after updating.

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
Ohdear IntegrationDrupal extension
Affected:< 2.0.4

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Verify OhDear Integration module is installed
    Run 'drush pm-list' or check the Drupal admin UI at /admin/modules to confirm the Ohdear Ohdear Integration module is present
    Affected if Module is not installed - not affected
  2. Check installed module version
    Run 'drush pm-info ohdear_ohdear_integration' or check the module's .info.yml file in modules/custom/ or modules/contrib/ for the version number
    Affected if Version is present and less than 2.0.4 - likely affected
  3. Confirm module is enabled
    Run 'drush state-get system.module' or check /admin/modules to verify the module is enabled
    Affected if Module is disabled - not affected since the vulnerable code is not executing
  4. Review role permissions for OhDear module
    Access /admin/people/permissions and examine any permissions granted related to OhDear Integration. Check user roles that have access to protected Drupal administrative paths
    Affected if Any authenticated user or low-privilege role has access to paths/resources they should not reach - indicates exploitation of the access control flaw

You are affected if the OhDear Integration module is installed, enabled, and running a version before 2.0.4, especially if untrusted users can access protected administrative paths.

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 2.0.4 or later
Fixed in 2.0.4
Interim mitigation

Update the OhDear Integration module to version 2.0.4 or later to remediate the authorization bypass. Review user role permissions after updating.

Recommended fix High confidence

2.0.4

  1. Back up your Drupal site database and files before making any changes
  2. Update the OhDear Integration module using Composer: run 'composer update drupal/ohdear' or specify version 2.0.4 with 'composer require drupal/ohdear:^2.0.4'
  3. Alternatively, update via Drupal admin UI at /admin/modules if composer is not used
  4. Run database updates if prompted: 'drush updb' or via admin UI at /update.php
  5. Clear Drupal caches: 'drush cr' or via admin UI at /admin/config/development/performance

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

Fix this in Ohdear Integration Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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