Vulnerability in course context (CVE-2020-25629)

Summary

Vulnerability in course context (CVE-2020-25629). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 3.9.2 or later.

Original description

The description as published by the source.

A vulnerability was found in Moodle where users with "Log in as" capability in a course context (typically, course managers) may gain access to some site administration capabilities by "logging in as" a System manager. This affects 3.9 to 3.9.1, 3.8 to 3.8.4, 3.7 to 3.7.7, 3.5 to 3.5.13 and earlier unsupported versions. This is fixed in 3.9.2, 3.8.5, 3.7.8 and 3.5.14.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-25629 has been found in course context.
Successful exploitation can lead to full system takeover.
What to do: upgrade course context to 3.9.2 or later.
If unsure, ask your IT team or search "course context CVE-2020-25629" on the vendor's site.

CVE-2020-25629 (course context)
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.9.2 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in course context.

📍 Affected scope

Check the vendor advisory for the affected versions of course context.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.9.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで course context を使っているサービスとバージョンを洗い出す。
2
Apply patch patch
```
Upgrade course context to 3.9.2
```
ステージング環境で 3.9.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami moodle

[{"type":"SEMVER","events":[{"introduced":"3.5.0"},{"fixed":"3.5.14"},{"introduced":"3.7.0"},{"fixed":"3.7.8"},{"introduced":"3.8.0"},{"fixed":"3.8.5"},{"introduced":"3.9.0"},{"fixed":"3.9.2"}]}]

References

advisory moodle.org
web nvd.nist.gov