Wordpress Learning Management SystemWordPress extension · Vibethemes
CVE-2023-36690
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 · uneditedCross-Site Request Forgery (CSRF) vulnerability in VibeThemes WPLMS theme <= 4.900 versions.
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 confidenceCross-Site Request Forgery (CSRF) vulnerability in the VibeThemes WPLMS WordPress theme affecting all versions up to and including 4.900. CSRF attacks exploit the trust a web application has in an authenticated user's browser by tricking them into submitting unintended requests.
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
<= 4.900CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check WPLMS theme version in WordPress adminNavigate to Appearance > Themes in the WordPress admin dashboard and locate the WPLMS theme. The installed version will be displayed there.Affected if The displayed version is 4.900 or lower (e.g., 4.900, 4.8, 4.7, etc.)
-
Verify theme version via style.cssAccess the theme files via FTP or file manager. Navigate to /wp-content/themes/wplms/style.css and locate the 'Version:' declaration in the file header.Affected if The version number found is 4.900 or lower.
-
Identify state-changing operations in theme filesSearch theme PHP files for form submissions and AJAX actions. Look for functions that modify data: post creation, user profile updates, course enrollments, or settings changes. Check if these operations include wp_verify_nonce or check_admin_referer calls.Affected if State-changing actions exist without nonce verification (nonce fields or checks are missing).
-
Check AJAX handlers for CSRF protectionExamine the theme's AJAX handlers (typically in main theme PHP files or includes/ajax.php). Look for admin-ajax.php actions and verify each handler calls nonce verification before processing requests.Affected if AJAX handlers process requests without validating nonces or checking user capabilities.
You are affected if the WPLMS theme version is 4.900 or lower AND your site has state-changing operations (forms, AJAX calls) that lack CSRF token verification.
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 anti-CSRF tokens (nonces) on all state-changing operations, verify Origin/Referer headers, and consider implementing SameSite cookie attributes. Upgrade to any available patched version above 4.900 if released.
Fix this in Wordpress Learning Management System
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-36690 — 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-2023-36690 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