Subscriber-level authorization bypass via user-controlled object key
Published Mar 19, 2026 · Updated Mar 19, 2026
IDOR in Themeum Tutor LMS 3.9.4 and earlier allows remote authenticated users to perform unauthorized actions through a user-controlled key. Published records do not identify the affected endpoint, object type, operation, or parameter beyond that key. Subscriber-level access is sufficient; the exact unauthorized action and affected data remain undisclosed, so the consequence cannot be bounded more narrowly.
Summary
What happened
IDOR in Themeum Tutor LMS 3.9.4 and earlier allows remote authenticated users to perform unauthorized actions through a user-controlled key. Published records do not identify the affected endpoint, object type, operation, or parameter beyond that key. Subscriber-level access is sufficient; the exact unauthorized action and affected data remain undisclosed, so the consequence cannot be bounded more narrowly.
The record
- CVE
- CVE-2025-32223
- Published
- Mar 19, 2026
- Updated
- Mar 19, 2026
- Vendor
- Themeum
- Product
- Tutor LMS
- Classifications
- CWE-639, CAPEC-180
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 19, 2026CVE publishedPublication date reported by the CVE source.
- Mar 19, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=n/a <=3.9.4 changes=[{"at":"3.9.5","status":"unaffected"}]
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo