CVE-2026-25372
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 · uneditedMissing Authorization 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.5.3.
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 confidenceAcademy LMS contains a missing authorization vulnerability where access control security levels are incorrectly configured, allowing authenticated users to access functionality or resources beyond their intended privilege level. The vulnerability stems from improper or missing authorization checks on certain endpoints or actions within the Learning Management System.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Confirm Academy LMS installation and versionLocate the Academy LMS installation directory and check version.php, composer.json, or the admin dashboard 'About' page. Compare the installed version against any known version releases.Affected if Academy LMS is installed and running without documented security patches applied.
-
Identify access control configuration filesSearch the application root for configuration files related to authentication, authorization, roles, or permissions (commonly found in /app/Config, /application/config, or similar paths under names like auth.php, permission.php, roles.php, or access_control.php).Affected if Authorization configuration files exist but lack explicit role-based access checks on sensitive endpoints.
-
Review defined user roles and privilege levelsExamine the role definitions in the database (often in tables named users, user_roles, roles, or permissions) or configuration files. List all defined roles and their associated permission levels.Affected if Multiple user roles exist with unclear or overlapping privilege boundaries that permit escalation.
-
Inspect endpoint access control enforcementReview the code for sensitive endpoints (admin functions, user data access, course management, payment processing) to verify that authorization checks (e.g., role verification, permission validation) are present and enforced before executing the action.Affected if Sensitive endpoints lack proper authorization middleware or permission checks before executing privileged operations.
-
Test for privilege escalation via lower-privileged accountsUsing a non-administrator account, attempt to access or modify resources intended for higher-privileged roles (admin-only functions, other users data, system settings). Observe whether the application permits or denies the action.Affected if Lower-privileged authenticated users can successfully access or modify resources outside their assigned role permissions.
A user is affected if Academy LMS is running and allows authenticated users to perform actions or access resources beyond the permissions explicitly assigned to their user role.
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 and enforce proper role-based access control (RBAC) checks on all sensitive endpoints and functionality. Audit the existing access control configuration to identify and remediate the security level misconfigurations.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25372 — 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-2026-25372 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