CVE-2025-67259
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 · uneditedA Broken Access Control vulnerability exists in ClassroomIO v0.1.13 where an authenticated low-privileged "student" user can access unauthorized course-level information by modifying intercepted API requests. Changing a captured POST request to a GET request against the /rest/v1/course PostgREST endpoint results in disclosure of sensitive information including other students details, tutor/admin profiles, and internal course metadata.
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 confidenceIn ClassroomIO v0.1.13, an authenticated student user can bypass authorization checks by intercepting a POST request to the /rest/v1/course PostgREST endpoint and changing it to a GET request. This Insecure Direct Object Reference (IDOR) flaw allows low-privileged users to retrieve sensitive data including other students' personal details, tutor and admin profiles, and internal course metadata that should be restricted to higher-privileged roles.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Identify ClassroomIO versionLocate the installed ClassroomIO version by checking package.json, container image tags, or the application itself (often displayed in UI footer or admin panel)Affected if version is 0.1.13 or falls within the initial release range where PostgREST integration was added without proper RBAC
-
Verify PostgREST endpoint exposureCheck application routing configuration or network traffic to confirm the /rest/v1/course endpoint is accessible. This is typically configured in the API gateway or reverse proxy settings.Affected if the /rest/v1/course endpoint is exposed and reachable from student-facing interfaces
-
Inspect role-based access control configurationReview the authorization configuration for the PostgREST endpoint, typically found in database RLS policies, API middleware, or PostgREST config. Look for role-specific access rules.Affected if authorization rules are missing, incomplete, or only enforced on certain HTTP methods (e.g., only POST) rather than all methods
-
Test for authorization bypass via HTTP method switchingUsing a tool like Burp Suite or curl, authenticate as a low-privileged student, then send a GET request to /rest/v1/course (or related data endpoints) and observe if sensitive data from other users or higher-privileged roles is returnedAffected if GET requests return data that should be restricted to higher-privileged roles (other students personal details, tutor/admin profiles, or internal metadata)
A user is affected if running ClassroomIO version 0.1.13 with an exposed PostgREST endpoint where authorization is not enforced uniformly across all HTTP methods.
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.
From vendor dataImplement proper role-based access control (RBAC) on the PostgREST endpoint to enforce authorization checks regardless of HTTP method, ensuring students can only access data explicitly permitted for their role.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-67259 — 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-2025-67259 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