CVE-2026-31914
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in hookandhook WP Courses LMS wp-courses allows DOM-Based XSS.This issue affects WP Courses LMS: from n/a through <= 3.2.26.
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 confidenceDOM-based Cross-site Scripting vulnerability in the WP Courses LMS WordPress plugin allows remote attackers to inject malicious JavaScript code through unsanitized input that is dynamically rendered in the browser without proper sanitization.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 Courses LMS plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Courses LMS' or check the filesystem at /wp-content/plugins/ for a folder containing 'wp-courses-lms'Affected if The plugin is present in the WordPress installation
-
Determine the installed plugin versionIn WordPress admin > Plugins > Installed Plugins, click on the plugin and view the version number displayed, or read the 'readme.txt' or 'wp-courses-lms.php' file in the plugin directory for the 'Version:' headerAffected if The version cannot be determined or is lower than the fixed version (compare to any official security release notes)
-
Identify user input points that render in the browserReview the plugin for any frontend forms, course creation fields, or user profile inputs (such as course titles, descriptions, lesson names, or user display fields) that accept and display user-supplied data without visible encodingAffected if There are input fields that output data directly to the page without apparent sanitization
-
Inspect DOM-rendered output for unsanitized contentUse browser developer tools (F12) > Elements or Console to examine if user-entered data from plugin forms appears in the page source as raw text (looking for unescaped HTML tags, script tags, or event handlers)Affected if User input is rendered as raw HTML or JavaScript in the page without encoding
If WP Courses LMS is installed and user-supplied data from plugin fields appears in the browser DOM without HTML entity encoding, the environment is affected by this DOM-based XSS vulnerability.
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 proper output encoding and input validation for all user-supplied data before DOM rendering; apply WordPress escape functions (esc_html, esc_attr, wp_kses) and consider Content Security Policy headers.
- 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-2026-31914 — 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-2026-31914 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