CVE-2025-63035
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 VibeThemes WPLMS wplms_plugin allows DOM-Based XSS.This issue affects WPLMS: from n/a through <= 1.9.9.5.4.
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 XSS vulnerability in WPLMS plugin allows execution of malicious JavaScript in victim's browser via unsanitized user input being rendered in web pages. The medium severity (6.5) suggests exploitation requires some user interaction or specific context.
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<= 1.9.9.5.4CVSS 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.
-
Confirm WPLMS plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WPLMS' or 'Vibethemes Wordpress Learning Management System' in the list of active pluginsAffected if WPLMS plugin is not installed or not active, the vulnerability does not apply
-
Check installed WPLMS versionIn WordPress admin, go to Plugins > Installed Plugins, find WPLMS, and note the version number displayed. Alternatively, check the version in the plugin's main PHP file header (typically wp-content/plugins/wplms/lms.php or similar)Affected if Version is 1.9.9.5.4 or lower; if version shows 1.9.9.5.5 or higher, the version may be patched
-
Identify if plugin processes user-supplied inputReview plugin settings and templates where user-generated content is displayed (such as course descriptions, assignment submissions, profile fields, or comments). Check if any of these accept and render input without visible sanitization in the frontend HTML sourceAffected if User input from course content, assignments, profiles, or comments is rendered directly in page HTML without encoding - this is the vulnerable condition for DOM XSS
-
Inspect browser DOM for unsanitized outputVisit a page where user input is displayed (e.g., course page, user profile), right-click > Inspect Element, and search for user-supplied text in the page source. Look for unescaped HTML characters like <, >, or quotes in attributesAffected if User-supplied text appears as raw HTML or JavaScript in the page source without entity encoding (e.g., appears as <script> rather than <script>)
Environment is affected if WPLMS plugin version is 1.9.9.5.4 or lower and the plugin processes and displays user input in web pages without proper output encoding.
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 input validation and output encoding on all user-supplied data before DOM rendering; update to patched version if available from vendor.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63035 — 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-63035 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