Security readout for executives and security teams
Plain-English summary
CVE-2025-65672 is an IDOR in classroomio 0.1.13 that can let an unauthenticated network attacker access course share and invite settings they should not see. The disclosed impact is confidentiality loss, not data modification or outage. Treat exposed classroomio deployments as a high-priority privacy and access-control issue.
Executive priority
High priority for organizations using classroomio because the issue can expose course sharing or invite configuration without authentication. If classroomio is not deployed, no direct action is indicated beyond documenting non-exposure.
Technical view
The record describes CWE-639 authorization bypass affecting course settings share and invite access in classroomio 0.1.13. CVSS 3.1 is 7.5, with network access, low complexity, no privileges, no user interaction, and high confidentiality impact. The provided sources do not name a patched version or vendor mitigation.
Likely exposure
Exposure is most likely in organizations running classroomio 0.1.13, especially internet-accessible instances. The CVE affected metadata lists vendor, product, and CPE as n/a, so teams should verify exposure through software inventory, repository lineage, and deployed package versions.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public references include the upstream classroomio repository and a CVE-specific GitHub repository, but the provided bundle does not establish exploitation in the wild.
Researcher notes
Evidence is limited to the CVE metadata and public GitHub references in the bundle. The record identifies classroomio 0.1.13 in the title and description, but structured affected fields are n/a. No patch, workaround, or active exploitation confirmation is provided.
Mitigation direction
Identify and prioritize any classroomio 0.1.13 deployments.
Check upstream classroomio and CVE guidance for a fixed release or advisory.
Restrict external access to affected classroomio instances where business allows.
Review and enforce object-level authorization on share and invite settings.
Monitor logs for unusual course settings share or invite access.
Validation and detection
Confirm whether deployed classroomio versions include 0.1.13.
Inventory internet-facing classroomio routes and access controls.
Review course settings share and invite authorization checks.
Audit recent access logs for unexpected course setting reads.
Track CVE updates for confirmed patch or mitigation details.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-639 · source CWE mapping
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.