CVE-2024-51658
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 Henrik Hoff WP Course Manager wp-course-manager allows Stored XSS.This issue affects WP Course Manager: from n/a through <= 1.3.
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 WP Course Manager plugin allows attackers to trick authenticated administrators into submitting malicious requests that inject persistent JavaScript code (Stored XSS) into the application. When other users view the affected pages, the injected script executes in their browsers, enabling session hijacking, credential theft, or administrative actions.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
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.
-
Verify WP Course Manager plugin is installedAccess WordPress admin panel, navigate to Plugins > Installed Plugins, and search for 'WP Course Manager'; or inspect /wp-content/plugins/ directory for a folder containing 'wp-course-manager' or similar namingAffected if The plugin appears in the installed plugins list
-
Confirm plugin is activeIn Plugins > Installed Plugins, verify the WP Course Manager plugin shows as 'Active'Affected if Plugin status is Active
-
Identify installed versionIn Plugins > Installed Plugins, click on the plugin to view details and read the Version number from the plugin header; alternatively, open the main plugin PHP file and look for 'Version:' in the plugin comment blockAffected if Version is unknown or within any range provided by the vendor (no specific affected versions listed in CVE)
-
Inspect database for stored XSS payloadsQuery WordPress database tables where course/lesson data is stored (typically wp_posts with post_type related to courses) for suspicious script tags, iframe elements, or event handlers like onload/onerror; use: SELECT * FROM wp_posts WHERE post_content LIKE '%<script%' OR post_content LIKE '%onerror=%'Affected if Any records contain unsanitized HTML/JavaScript that could execute in other users' browsers
-
Review plugin forms for nonce protectionInspect page source of any WP Course Manager admin forms (add/edit course, manage settings) and verify that awpnonce or similar nonce field is present in form markup; check that form action URLs include nonce verification endpointsAffected if Forms lack nonce fields or nonce validation is missing
You are affected if the WP Course Manager plugin is installed and active in your WordPress environment, as the CSRF-to-Stored-XSS vulnerability can allow attackers to inject malicious scripts through authenticated administrator sessions.
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 WordPress nonces on all state-changing forms and actions, verify nonce validity server-side, and apply proper output escaping/sanitization on all user-supplied data before rendering. Also audit and clean any existing stored malicious data.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-51658 — 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-2024-51658 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