CVE-2026-33703
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedChamilo LMS is a learning management system. Prior to 2.0.0-RC.3, an Insecure Direct Object Reference (IDOR) vulnerability in the /social-network/personal-data/{userId} endpoint allows any authenticated user to access full personal data and API tokens of arbitrary users by modifying the userId parameter. This results in mass disclosure of sensitive user information and credentials, enabling a full platform data breach. This vulnerability is fixed in 2.0.0-RC.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn IDOR vulnerability in the /social-network/personal-data/{userId} endpoint of Chamilo LMS allows any authenticated user to retrieve full personal data and API tokens of arbitrary users by simply manipulating the userId parameter in the request. The application fails to verify that the requesting user has authorization to access the specified user's data, enabling unauthorized access to sensitive credentials across the platform.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 2.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Chamilo LMS versionLocate the version file or admin panel that displays the installed Chamilo LMS version. This is typically found in the admin dashboard, a version.php file, or the system information page.Affected if The installed version is exactly 2.0.0 (the only affected version listed). Any version before or after may not be affected.
-
Verify the vulnerable endpoint existsCheck if the route /social-network/personal-data/{userId} is present in the application routing configuration or code structure. This endpoint should exist in the codebase for the vulnerability to apply.Affected if The endpoint /social-network/personal-data/{userId} is present and accessible within the application.
-
Test IDOR on personal data endpointLog in as a standard authenticated user. Make a GET request to /social-network/personal-data/ with a different userId (not your own) in the URL. Observe whether the response contains personal data or API tokens belonging to that other user.Affected if The endpoint returns personal data and API tokens for a userId that differs from the authenticated requesting user, confirming the authorization check is missing.
-
Check for authorization logic in endpoint codeReview the source code for the /social-network/personal-data/{userId} endpoint. Look for authorization or ownership verification logic that confirms the requesting user matches the requested userId.Affected if No code exists that validates the authenticated user is authorized to access the specified userId's data, or such validation is missing entirely.
You are affected if you are running Chamilo LMS version 2.0.0 and the /social-network/personal-data endpoint returns another user's data without proper authorization validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Chamilo LMS version 2.0.0-RC.3 or later. Until then, implement application-level authorization checks to ensure users can only access their own personal data, and consider temporarily restricting access to this endpoint.
2.0.0-RC.3
- 1. Create a complete backup of the current Chamilo LMS installation including all files and the database
- 2. Download Chamilo LMS version 2.0.0-RC.3 from the official GitHub repository or distribution channel
- 3. Extract the new version files
- 4. Replace the existing Chamilo installation files with the new 2.0.0-RC.3 files
- 5. Run any database migration scripts included in the upgrade if applicable
- 6. Clear any caches (application cache, session data) to ensure new code is loaded
- 7. Verify the /social-network/personal-data/{userId} endpoint now properly enforces authorization checks
- 8. Test that users can only access their own personal data and not other users' data
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33703 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data