dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2025-58668

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-22
Fix available
A fix is available. Upgrade to 4.971 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in VibeThemes WPLMS wplms allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WPLMS : from n/a through <= 4.970.

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

Missing authorization in WPLMS allows attackers to bypass access control checks due to incorrectly configured security levels. The vulnerability is exploitable without authentication and grants full access to sensitive functionality, leading to complete compromise of confidentiality, integrity, and availability.

MitigationUpdate to the patched version of WPLMS (beyond 4.970) and conduct a thorough audit of all access control configurations to ensure proper authorization enforcement across all user roles and endpoints.

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
Wordpress Learning Management SystemWordPress extension
Affected:< 4.971

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

CVSS:3.1/AV:N/AC:L/PR:N/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 WPLMS version installed
    Check the version number of the WPLMS plugin in WordPress admin under Plugins > Installed Plugins, or inspect the main plugin file header (typically wp-content/plugins/wplms/languages/wplms.pot or the main plugin file) for the Version field
    Affected if The installed version is lower than 4.971 (e.g., 4.970, 4.96, 4.9, etc.)
  2. Verify WPLMS plugin is active
    Confirm the WPLMS plugin is enabled in WordPress under Plugins > Installed Plugins. The vulnerability only applies if the plugin is installed and active
    Affected if WPLMS plugin is installed and activated on the WordPress site
  3. Test unauthenticated access to sensitive endpoints
    Attempt to access common WPLMS administrative or sensitive endpoints without logging in (e.g., /wp-admin/admin-ajax.php actions related to WPLMS, WPLMS API endpoints, or course/assignment management URLs). Use a tool like curl or Burp to send requests without authentication cookies
    Affected if The server returns successful responses or sensitive data without requiring authentication credentials
  4. Inspect user role configuration
    Check WordPress user roles and capabilities under Users > Users in admin, and review if WPLMS has created custom roles with elevated permissions. Examine the wp_usermeta table or use a database query to review capability assignments for roles like 'student', 'instructor', 'tutor'
    Affected if Users with low-privilege roles (e.g., students or unauthenticated users) have capabilities that should be restricted to administrators or instructors

You are affected if WPLMS version is below 4.971 AND the plugin is active AND unauthorized users can access sensitive WPLMS functionality without authentication.

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 4.971 or later
Fixed in 4.971
Interim mitigation

Update to the patched version of WPLMS (beyond 4.970) and conduct a thorough audit of all access control configurations to ensure proper authorization enforcement across all user roles and endpoints.

Recommended fix High confidence

WPLMS version 4.971 or later

  1. 1. Create a complete backup of the WordPress site including database and files
  2. 2. Update the WPLMS plugin to version 4.971 or the latest available version through WordPress admin dashboard (Plugins > All Plugins > WPLMS > Update Now)
  3. 3. Alternatively, upload the new WPLMS version manually via Plugins > Add New > Upload Plugin
  4. 4. After update, verify the version number reflects 4.971 or higher in Plugins > Installed Plugins
  5. 5. Test critical LMS functions (course enrollment, student access, instructor permissions) to confirm normal operation
Caveat Review changelog for any template or custom code changes that may require updates to custom themes or child themes

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

Fix this in Wordpress Learning Management System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing12.0 h
  • Review / QA6.0 h
44.0 hours of engineering $7,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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