# CVE-2024-25983: Msa-24-0006: idor on dashboard comments block

> Attackers can add comments to other users' dashboard blocks via insufficient web service checks, allowing unauthorized data modification.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 19 Feb 2024
- **Updated:** 1 Aug 2024
- **Also known as:** BIT-moodle-2024-25983, GHSA-9r26-5w88-qhp9, UBUNTU-CVE-2024-25983

## What is CVE-2024-25983?

CVE-2024-25983 is a low-severity missing authorization vulnerability in Fedoraproject Fedora, published on 19 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Insufficient checks in a web service made it possible to add comments to the comments block on another user's dashboard when it was not otherwise available (e.g., on their profile page).

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

7 open source packages ship an affected version, including moodle/moodle and moodle. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `moodle/moodle` | Packagist | All versions | 4.1.9 |
| `moodle/moodle` | Packagist | All versions | 4.1.9 |
| `moodle/moodle` | Packagist | From 4.2.0 | 4.2.6 |
| `moodle/moodle` | Packagist | From 4.2.0 | 4.2.6 |
| `moodle/moodle` | Packagist | From 4.3.0 | 4.3.3 |
| `moodle/moodle` | Packagist | From 4.3.0 | 4.3.3 |
| `moodle` | Bitnami | All versions | 4.1.9, 4.2.6, 4.3.3 |

Products: Fedoraproject Fedora, Moodle Moodle.

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

Upgrade moodle/moodle to a fixed version for your release line: 4.1.9, 4.2.6 or 4.3.3.

## Is CVE-2024-25983 being exploited?

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

## Other vulnerabilities in Fedoraproject Fedora

- [CVE-2024-4577](https://insights.sbomify.com/CVE-2024-4577/): PHP-CGI OS Command Injection (critical 9.8, exploited in the wild)
- [CVE-2021-39226](https://insights.sbomify.com/CVE-2021-39226/): Grafana Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2019-5544](https://insights.sbomify.com/CVE-2019-5544/): VMware ESXi and Horizon DaaS OpenSLP Heap-Based Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2024-4947](https://insights.sbomify.com/CVE-2024-4947/): Google Chromium V8 Type Confusion (critical 9.6, exploited in the wild)
- [CVE-2024-4671](https://insights.sbomify.com/CVE-2024-4671/): Google Chromium Visuals Use-After-Free (critical 9.6, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-25983 is a low-severity missing authorization vulnerability in Fedoraproject Fedora, published on 19 Feb 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-25983 in the wild and no public exploit code.

Affected packages and fixed versions:
- moodle/moodle (Packagist): affected all versions; fixed in 4.1.9
- moodle/moodle (Packagist): affected all versions; fixed in 4.1.9
- moodle/moodle (Packagist): affected from 4.2.0; fixed in 4.2.6
- moodle/moodle (Packagist): affected from 4.2.0; fixed in 4.2.6
- moodle/moodle (Packagist): affected from 4.3.0; fixed in 4.3.3
- moodle/moodle (Packagist): affected from 4.3.0; fixed in 4.3.3
- moodle (Bitnami): affected all versions; fixed in 4.1.9, 4.2.6, 4.3.3

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-25983/ (Markdown: https://insights.sbomify.com/CVE-2024-25983/index.md)
```

## Sources

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

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