dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-59562

MEDIUM · 5.5 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Authorization Bypass Through User-Controlled Key vulnerability in Kodezen LLC Academy LMS academy allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Academy LMS: from n/a through <= 3.3.4.

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 · moderate confidence

Academy LMS versions through 3.3.4 contain an authorization bypass vulnerability where a user-controlled key parameter allows attackers to circumvent access control security levels. This appears to be an Insecure Direct Object Reference (IDOR) or broken access control flaw where the application trusts client-supplied identifiers without proper server-side authorization verification.

MitigationImplement server-side authorization checks that verify the authenticated user's permissions before allowing access to any resource identified by user-controlled keys. Use indirect references and enforce role-based access control consistently across all endpoints.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Academy LMS version
    Check the version number in the admin dashboard (typically under System Settings > General or About page), or inspect the application config file (commonly application/config/constants.php or a version.php file in the root directory)
    Affected if version is 3.3.4 or any earlier version (3.x release)
  2. Locate user-controlled key endpoints
    Review application source code for endpoints that accept object identifiers (IDs) as URL parameters (e.g., ?id=123, /course/123, /user/123) without proper server-side validation
    Affected if endpoints accept numeric or GUID identifiers directly from request parameters to fetch sensitive data
  3. Verify authorization on sensitive modules
    Test access to admin/instructor-level features (course creation, user management, grade editing) using a regular user account by manipulating object IDs in requests. Use browser developer tools or curl to modify the identifier in the request
    Affected if a lower-privileged user can access, modify, or delete objects belonging to higher-privileged users by changing the object ID parameter
  4. Inspect authentication middleware
    Examine the codebase for access control functions (checkPermission, verifyOwnership, isAuthorized) and verify they are called BEFORE object retrieval. Check controller files in application/controllers/ for proper authorization logic
    Affected if controllers retrieve objects using user-supplied IDs without calling authorization validation functions first, or if such functions are missing entirely
  5. Review role-based access control configuration
    Check database tables related to roles and permissions (commonly role_permissions, user_roles, or similar) and verify that role checks are enforced consistently across all controllers
    Affected if some endpoints lack role verification or allow privilege escalation through IDOR

A user is affected if they run Academy LMS version 3.3.4 or earlier AND the application exposes endpoints that accept user-controlled object identifiers without server-side authorization verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side authorization checks that verify the authenticated user's permissions before allowing access to any resource identified by user-controlled keys. Use indirect references and enforce role-based access control consistently across all endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59562 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59562 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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