Vulnerability in Chamilo LMS (CVE-2026-33736)
Summary
Vulnerability in Chamilo LMS (CVE-2026-33736). Confidential information can be exposed externally. Exploitable via GET /api/users. Mitigation: upgrade to 2.0.0-RC.3 or later.
Original description
The description as published by the source.
Chamilo LMS is a learning management system. Prior to 2.0.0-RC.3, any authenticated user (including ROLE_STUDENT) can enumerate all platform users and access personal information (email, phone, roles) via GET /api/users, including administrator accounts. This vulnerability is fixed in 2.0.0-RC.3.
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-2026-33736 has been found in Chamilo LMS.
Attackers can target a specific entry point like GET /api/users over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade Chamilo LMS to 2.0.0-RC.3 or later.
If unsure, ask your IT team or search "Chamilo LMS CVE-2026-33736" on the vendor's site.
CVE-2026-33736 (Chamilo LMS) — CWE-639
Attack vector: remote (network-reachable) / no user interaction
Attack surface: GET /api/users
Patched: 2.0.0-RC.3 — 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.
A vulnerability (CWE-639) exists in Chamilo LMS. Attackers reach the vulnerable code path via GET /api/users.
Check the vendor advisory for the affected versions of Chamilo LMS. Attack surface: GET /api/users.
Severity: ?. Confidential information can be exposed externally.
Update to 2.0.0-RC.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/users requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Chamilo LMS を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'GET /api/users' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/usersへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade Chamilo LMS to 2.0.0-RC.3ステージング環境で 2.0.0-RC.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/users on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- patch github.com