# CVE-2022-40316: Moodle No groups filtering in H5P activity attempts report

> Non-editing teachers can view H5P activity attempts from groups they should not access when separate groups mode is enabled.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Sep 2022
- **Updated:** 20 May 2025
- **Also known as:** BIT-moodle-2022-40316, GHSA-385f-vgq7-8hhx, UBUNTU-CVE-2022-40316

## What is CVE-2022-40316?

CVE-2022-40316 is a medium-severity vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 30 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The H5P activity attempts report did not filter by groups, which in separate groups mode could reveal information to non-editing teachers about attempts/users in groups they should not have access to.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-40316?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `moodle/moodle` | Packagist | From 3.11 | 3.11.10 |
| `moodle/moodle` | Packagist | From 3.11 | 3.11.10 |
| `moodle/moodle` | Packagist | From 3.9 | 3.9.17 |
| `moodle/moodle` | Packagist | From 3.9 | 3.9.17 |
| `moodle/moodle` | Packagist | From 4.0 | 4.0.4 |
| `moodle/moodle` | Packagist | From 4.0 | 4.0.4 |
| `moodle` | Bitnami | From 3.9.0 | 3.9.17, 3.11.10, 4.0.4 |

Products: Fedoraproject Extra Packages for Enterprise Linux, Fedoraproject Fedora, Moodle Moodle.

## How do I fix CVE-2022-40316?

Upgrade moodle/moodle to a fixed version for your release line: 3.11.10, 3.9.17 or 4.0.4.

## Is CVE-2022-40316 being exploited?

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

## Other vulnerabilities in Fedoraproject Extra Packages for Enterprise Linux

- [CVE-2023-34152](https://insights.sbomify.com/CVE-2023-34152/): Command injection in ImageMagick (critical 9.8)
- [CVE-2022-4170](https://insights.sbomify.com/CVE-2022-4170/): Code injection in rxvt-unicode (critical 9.8)
- [CVE-2022-40315](https://insights.sbomify.com/CVE-2022-40315/): Moodle Minor SQL injection risk in admin user browsing (critical 9.8)
- [CVE-2022-45152](https://insights.sbomify.com/CVE-2022-45152/): Moodle blind Server-Side Request Forgery (SSRF) vulnerability in LTI provider library (critical 9.1)
- [CVE-2022-24882](https://insights.sbomify.com/CVE-2022-24882/): Server side NTLM does not properly check parameters in FreeRDP (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40316 and fix it if it is affected.

What it is: CVE-2022-40316 is a medium-severity vulnerability in Fedoraproject Extra Packages for Enterprise Linux, published on 30 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40316 in the wild and no public exploit code.

Affected packages and fixed versions:
- moodle/moodle (Packagist): affected from 3.11; fixed in 3.11.10
- moodle/moodle (Packagist): affected from 3.11; fixed in 3.11.10
- moodle/moodle (Packagist): affected from 3.9; fixed in 3.9.17
- moodle/moodle (Packagist): affected from 3.9; fixed in 3.9.17
- moodle/moodle (Packagist): affected from 4.0; fixed in 4.0.4
- moodle/moodle (Packagist): affected from 4.0; fixed in 4.0.4
- moodle (Bitnami): affected from 3.9.0; fixed in 3.9.17, 3.11.10, 4.0.4

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

## Sources

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

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