CVE-2026-5348
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 · uneditedThe Academy LMS – WordPress LMS Plugin for Complete eLearning Solution plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 3.8.1. This is due to the '/topics' REST API endpoint being registered with a permission callback set to '__return_true', allowing unauthenticated access to course curriculum data without verifying the course's post status or user enrollment. This makes it possible for unauthenticated attackers to access detailed curriculum information for private, draft, scheduled, or password-protected courses by enumerating course IDs.
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 confidenceThe Academy LMS WordPress plugin registers a '/topics' REST API endpoint with a permission callback set to '__return_true', which unconditionally allows any unauthenticated request. This endpoint returns course curriculum data without verifying the course's post status (private, draft, scheduled, password-protected) or checking user enrollment, enabling attackers to enumerate course IDs and access sensitive course materials.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Confirm Academy LMS plugin installationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Academy LMS', or check if the /wp-content/plugins/academy directory exists on the serverAffected if Academy LMS plugin is present in the WordPress installation
-
Determine Academy LMS versionView the plugin version in the plugin admin panel, or read the version from the plugin header in file /wp-content/plugins/academy/academy.phpAffected if The installed version matches any version of Academy LMS (the vulnerability exists in the plugin when the /topics endpoint is registered)
-
Test unauthenticated access to the /topics REST API endpointSend a GET request to https://yourdomain.com/wp-json/academy/v1/topics with a course_id parameter, for example: /wp-json/academy/v1/topics?course_id=1, using no authentication headersAffected if The request returns HTTP 200 with course curriculum data (lessons, topics, attachments) without requiring authentication
-
Verify if private or draft course content is exposedCreate a course set to 'Private', 'Draft', or 'Scheduled' status, then query the /topics endpoint using that course's ID without being logged inAffected if The endpoint returns curriculum data for non-published courses to unauthenticated users
-
Confirm enrollment is not verifiedQuery the /topics endpoint for a course the requesting user is not enrolled in, without being logged inAffected if The endpoint returns full curriculum content regardless of enrollment status
If the Academy LMS plugin is installed and the /topics REST API endpoint returns course curriculum data to unauthenticated requests, including private or non-enrolled course content, the environment is affected by this vulnerability.
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 dataReplace the '__return_true' permission callback with a custom function that verifies the course status is 'publish' AND confirms user enrollment before returning curriculum data, or update to a patched version if available from the vendor.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5348 — 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-5348 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