CVE-2024-34006
Moodle ≤ 4.1.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:NSummary
CVE-2024-34006 is a medium-severity Inappropriate Encoding for Output Context (CWE-838) vulnerability in Moodle Moodle. Its CVSS base score is 4.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 28th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-15 (Information Output Filtering) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-1818
Vulnerability Data
The site log report required additional encoding of event descriptions to ensure any HTML in the content is displayed in plaintext instead of being rendered.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.1V1.2.2V1.2.3V1.2.5
Mitigating Controls (NIST 800-53 r5) AI
Validates output data representations to ensure consistency with expected formats, directly stopping encoding mismatches for downstream contexts.
Requires application of secure engineering principles during development that include correct output encoding for context.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require correct output encoding to match downstream context, but eliminating only this flaw covers a narrow slice of the broader control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure coding directly addresses proper output encoding for context, covering most of the weakness and the control's intent.
Security testing can detect encoding mismatches, but testing alone does not prevent the weakness at source.
Secure development life cycle requires encoding-aware output handling, but does not mandate context-specific encoding checks.
Application security requirements can specify correct output encoding, yet the control is broader than this single weakness.