Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2025-49925
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 VibeThemes WPLMS wplms_plugin allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects WPLMS: from n/a through <= 1.9.9.7.
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 confidenceMissing Authorization vulnerability in the WPLMS WordPress plugin allows attackers to access functionality that should be restricted by Access Control Lists (ACLs). The issue affects versions up to and including 1.9.9.7, potentially allowing unauthenticated or unauthorized users to perform privileged actions. With a CVSS score of 7.5, this is a network-exploitable vulnerability that does not require authentication to exploit.
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
< 1.9.9.8CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 WPLMS plugin installationNavigate to WordPress Admin > Plugins and look for 'WPLMS - WordPress Learning Management System' or inspect the plugin directory (wp-content/plugins/wplms)Affected if The WPLMS plugin is installed and active
-
Identify installed WPLMS versionCheck the plugin version in the WordPress Plugins admin page, or open the main plugin file (typically wplms.php) and look for the 'Version' header in the plugin comment blockAffected if The installed version is lower than 1.9.9.8 (e.g., 1.9.9.7, 1.9.9.6, etc.)
-
Inspect access control on sensitive plugin actionsReview the plugin code for AJAX actions or admin pages that perform privileged operations (create_user, update_course, modify_member, etc.) and verify if they include current_user_can() capability checks or nonce verificationAffected if Privileged actions lack capability checks or nonce validation, allowing unauthorized access
-
Test unauthenticated access to protected functionalityIf safe to do in a test environment, attempt to access known WPLMS endpoints or trigger sensitive actions without providing authentication credentialsAffected if Unauthenticated requests successfully execute privileged operations that should require authorization
A user is affected if they have WPLMS version 1.9.9.7 or earlier installed AND the plugin exposes unprotected endpoints that allow unauthorized users to perform privileged actions.
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.
dbcve · scoped1.9.9.8
Update to the latest version of WPLMS when a patch is released. If no patch is available, conduct a code review to identify all unprotected endpoints and implement proper capability checks and nonce verification to restrict access to authorized users only.
1.9.9.8
- Log in to your WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Locate the WPLMS plugin in the list
- Check the current version number to confirm it is 1.9.9.7 or earlier
- If an update is available, click 'Update Now' to upgrade to version 1.9.9.8
- Alternatively, navigate to Dashboard > Updates and apply all available updates
- After updating, verify the new version number reflects 1.9.9.8
- Test critical LMS functionality (course creation, student enrollment, quiz submissions) to ensure the update did not break existing features
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wordpress Learning Management System
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49925 — 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-2025-49925 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