dbcve.org
Academy LmsWordPress extension · Kodezen

CVE-2024-38701

HIGH · 8.8 CVSS v3.1 Published 2024-07-22
Fix available
A fix is available. Upgrade to 2.0.5 or later.
See remediation →
94/100
Remediation priority · Urgent
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 Academy LMS.This issue affects Academy LMS: from n/a through 2.0.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

Authorization bypass vulnerability in Academy LMS where user-controlled input (likely request parameters containing identifiers or keys) is used to access resources without proper authorization validation. This allows authenticated users to potentially access or modify other users' data by manipulating these keys.

MitigationImplement proper server-side authorization checks validating user permissions before allowing access to any resource. Replace direct object references with indirect references and ensure all endpoints validate the current user's ownership or permissions for requested resources.

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
Academy LmsWordPress extension
Affected:< 2.0.5

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the Kodezen Academy LMS installation
    Locate the version file or check the admin dashboard for the installed version. Common locations include a version.php file in the application root, composer.json, or the 'About' or 'System Info' section in the admin panel.
    Affected if The version cannot be determined or is not displayed in the expected locations, making it unclear whether the installation is patched.
  2. Compare installed version to affected range
    Determine the exact version number from step 1 and compare it to the affected range: Kodezen Academy Lms version < 2.0.5
    Affected if The installed version is any version below 2.0.5, indicating the vulnerability is present.
  3. Identify endpoints using user-controlled identifiers
    Review application source code or proxy HTTP traffic to identify API endpoints or pages that accept user-provided identifiers (such as user IDs, record IDs, or keys) as request parameters for accessing data.
    Affected if Endpoints accept identifiers directly from request parameters without additional ownership verification.
  4. Verify authorization logic for resource access
    Inspect the code handling requests with user-supplied identifiers. Check whether the application validates that the authenticated user owns or has permission to access the requested resource before returning data.
    Affected if No server-side authorization check exists, or the check can be bypassed by manipulating identifier values in the request.
  5. Test for horizontal privilege escalation
    Using an authenticated user account, modify identifier values in requests to access resources belonging to other users. For example, if a request includes 'user_id=123' or 'record_id=456', attempt to access data by changing these values to different numbers.
    Affected if The application returns data for resources owned by other users when identifiers are manipulated, confirming the authorization bypass.

If Kodezen Academy LMS version is below 2.0.5 and endpoints accept user-controlled identifiers without proper ownership validation, the installation is affected by this authorization bypass.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0.5 or later
Fixed in 2.0.5
Interim mitigation

Implement proper server-side authorization checks validating user permissions before allowing access to any resource. Replace direct object references with indirect references and ensure all endpoints validate the current user's ownership or permissions for requested resources.

Recommended fix High confidence

Academy LMS 2.0.5

  1. Upgrade Academy LMS to version 2.0.5 or later to address the IDOR vulnerability

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Academy Lms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-38701 — 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-2024-38701 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