Chamilo LMS up to 1.11.37/2.0.0-RC.2 lp_ajax_save_item.php authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Chamilo LMS up to 1.11.37/2.0.0-RC.2. Affected by this vulnerability is an unknown functionality of the file lp_ajax_save_item.php. This manipulation causes authorization. This vulnerability is tracked as CVE-2026-33702. The attack is possible to be carried out remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability has been found in Chamilo LMS up to 1.11.37/2.0.0-RC.2 and classified as problematic. Affected by this vulnerability is an unknown functionality of the file lp_ajax_save_item.php. The manipulation with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect integrity, and availability. The summary by CVE is:
Chamilo LMS is a learning management system. Prior to 1.11.38 and 2.0.0-RC.3, Chamilo LMS contains an Insecure Direct Object Reference (IDOR) vulnerability in the Learning Path progress saving endpoint. The file lp_ajax_save_item.php accepts a uid (user ID) parameter directly from $_REQUEST and uses it to load and modify another user's Learning Path progress — including score, status, completion, and time — without verifying that the requesting user matches the target user ID. Any authenticated user enrolled in a course can overwrite another user's Learning Path progress by simply changing the uid parameter in the request. This vulnerability is fixed in 1.11.38 and 2.0.0-RC.3.
The advisory is shared at github.com. This vulnerability is known as CVE-2026-33702 since 03/23/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.
By approaching the search of inurl:lp_ajax_save_item.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 1.11.38 or 2.0.0-RC.3 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 1.11.0
- 1.11.1
- 1.11.2
- 1.11.3
- 1.11.4
- 1.11.5
- 1.11.6
- 1.11.7
- 1.11.8
- 1.11.9
- 1.11.10
- 1.11.11
- 1.11.12
- 1.11.13
- 1.11.14
- 1.11.15
- 1.11.16
- 1.11.17
- 1.11.18
- 1.11.19
- 1.11.20
- 1.11.21
- 1.11.22
- 1.11.23
- 1.11.24
- 1.11.25
- 1.11.26
- 1.11.27
- 1.11.28
- 1.11.29
- 1.11.30
- 1.11.31
- 1.11.32
- 1.11.33
- 1.11.34
- 1.11.35
- 1.11.36
- 1.11.37
- 2.0.0-RC.0
- 2.0.0-RC.1
- 2.0.0-RC.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.1
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: LMS 1.11.38/2.0.0-RC.3
Timeline
03/23/2026 CVE reserved04/10/2026 Advisory disclosed
04/10/2026 VulDB entry created
04/10/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-33702 (🔒)
GCVE (CVE): GCVE-0-2026-33702
GCVE (VulDB): GCVE-100-356917
Entry
Created: 04/10/2026 20:40Changes: 04/10/2026 20:40 (64)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.