# Moodle CSRF risks due to misuse of confirm_sesskey

Advisory record · `GHSA-356g-7x36-7m34`

- **Identifiers:** `GHSA-356g-7x36-7m34` · `BIT-moodle-2024-38276` · `CVE-2024-38276` · `PKSA-pwh8-w7s1-zt49`
- **State:** Confirmed
- **Severity:** CVSS 5.4 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-352](https://cwe.mitre.org/data/definitions/352.html)
- **Tags:** [Cross-site request forgery (CSRF)](https://agentprime.io/advisories/tag/csrf.md)
- **Published:** 18 Jun 2024
- **Updated:** 9 Aug 2024
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 18 Jun 2024, 21:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `moodle/moodle` (Packagist): affected `>=4.4.0-beta, <4.4.1 || >=4.3.0-beta, <4.3.5 || >=4.2.0-beta, <4.2.8 || <4.1.11`; fixed in `4.4.1`, `4.3.5`, `4.2.8`, `4.1.11`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.4 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`, from GitHub Advisory Database

- **CISA KEV:** Not listed.
- **EPSS:** 0.0046, the 40th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 18 Jun 2024. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-356g-7x36-7m34](https://github.com/advisories/GHSA-356g-7x36-7m34)
- [OSV: GHSA-356g-7x36-7m34](https://osv.dev/vulnerability/GHSA-356g-7x36-7m34)
- <https://nvd.nist.gov/vuln/detail/CVE-2024-38276>
- <https://github.com/moodle/moodle/commit/f2807dee5bc777d9c58b7a70cba6e4c21ee02ea1>
- <https://github.com/moodle/moodle/commit/e23f603c41055ab92f9b430cf0e7a54b4e120f95>
- <https://github.com/moodle/moodle/commit/e1dab5f38166a2ff62983178f7bf8f0ed3a61090>
- <https://github.com/moodle/moodle/commit/dc84fcfab06a4a0fe37797b8422e9fe3a1031c3e>
- <https://github.com/moodle/moodle/commit/da8e8cee6ffaf7c184eded97e1016f20c9de0561>
- <https://github.com/moodle/moodle/commit/c5b1604e8136db6d72057dd8052955058489206c>
- <https://github.com/moodle/moodle/commit/c1aacb3e2884ea4dcc221c5ef2e449ce345f78ae>
- <https://github.com/moodle/moodle/commit/c18b59808cefe7b54c85dce6bf2cc71601080667>
- <https://github.com/moodle/moodle/commit/a0d8c025f732d5c18a2b9d1a8e5cbee35dce86f4>
- <https://github.com/moodle/moodle/commit/9af9711c0a78ebad87d49bcb369ff813bc57d0a7>
- <https://github.com/moodle/moodle/commit/756090ed79aa056d0b5f58e7a1dff67f139f76b4>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-356g-7x36-7m34>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-356g-7x36-7m34/>. Everything for agents: <https://agentprime.io/llms.txt>.
