dbcve.org
VulnerabilityAwaiting classification

CVE-2026-10824

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
The Masteriyo LMS WordPress plugin before 2.2.1 does not perform authorization checks in a course-progress REST API controller, allowing unauthenticated users to read and permanently delete any user's course-progress records.

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 confidence

The Masteriyo LMS WordPress plugin before version 2.2.1 has a broken access control vulnerability in its course-progress REST API controller. The endpoint lacks authorization checks, enabling any unauthenticated user to read and permanently delete any user's course-progress records via direct object reference.

MitigationUpdate Masteriyo LMS to version 2.2.1 or later which includes proper authorization checks on the course-progress REST API endpoint.

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 checks

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

  1. Verify Masteriyo LMS plugin is installed
    Check the WordPress plugin directory for the masteriyo-lms folder, or query the site's plugins list via WP-CLI: wp plugin list --name=masteriyo-lms
    Affected if The plugin is not installed or not present on the system
  2. Determine installed plugin version
    Check the plugin main file header for the Version field, or run: wp plugin get masteriyo-lms --field=version
    Affected if The version is lower than 2.2.1 (e.g., 2.2.0, 2.1.x, etc.)
  3. Confirm WordPress REST API is accessible
    Send a GET request to /wp-json/ and verify the API responds. The REST API is enabled by default in WordPress.
    Affected if The REST API returns a valid JSON response (indicating it's enabled)
  4. Test course-progress endpoint authorization
    Send an unauthenticated GET request to /wp-json/masteriyo/v1/course-progress/ and check if it returns data. Then try DELETE on a specific progress ID like /wp-json/masteriyo/v1/course-progress/{id} to verify unauthenticated deletion is possible.
    Affected if The endpoint returns course progress data or succeeds with a DELETE request without requiring authentication (HTTP 200/204 instead of 401/403)

A user is affected if Masteriyo LMS version is below 2.2.1 AND the WordPress REST API is accessible to unauthenticated requests, allowing them to read or delete any course-progress records without authorization.

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

Update Masteriyo LMS to version 2.2.1 or later which includes proper authorization checks on the course-progress REST API endpoint.

Recommended fix Moderate confidence

Masteriyo LMS version 2.2.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find Masteriyo LMS in the plugin list
  4. If an update is available, click 'Update Now' to upgrade to version 2.2.1 or later
  5. Alternatively, go to Plugins > Add New > Upload Plugin and upload the latest version from wordpress.org
  6. After updating, verify the plugin version shows 2.2.1 or higher under Plugins > Installed Plugins
  7. Test course progress functionality to ensure the update did not break legitimate user workflows

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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