# CVE-2024-13290: OhDear Integration - Moderately critical - Access bypass - SA-CONTRIB-2024-056

> An attacker can bypass authorization controls in the Drupal OhDear Integration module to access restricted resources via forceful browsing.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jan 2025
- **Updated:** 14 Jan 2025
- **Also known as:** DRUPAL-CONTRIB-2024-056, GHSA-mxgx-9cvp-m653

## What is CVE-2024-13290?

CVE-2024-13290 is a medium-severity missing authorization vulnerability in Drupal OhDear Integration, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect Authorization vulnerability in Drupal OhDear Integration allows Forceful Browsing.This issue affects OhDear Integration: from 0.0.0 before 2.0.4.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-13290?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/ohdear_integration` | Packagist:https://packages.drupal.org/8 | All versions | 2.0.4 |

Products: Ohdear Ohdear Integration.

## How do I fix CVE-2024-13290?

Upgrade to a fixed version.

## Is CVE-2024-13290 being exploited?

There is no known exploitation of CVE-2024-13290 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-13290 and fix it if it is affected.

What it is: CVE-2024-13290 is a medium-severity missing authorization vulnerability in Drupal OhDear Integration, published on 9 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-13290 in the wild and no public exploit code.

Affected product: Drupal OhDear Integration. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-13290/ (Markdown: https://insights.sbomify.com/CVE-2024-13290/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-13290
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-13290
- OSV: https://osv.dev/vulnerability/CVE-2024-13290

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-13290/
Summaries are generated and may contain mistakes; the official description above is the record.