dbcve.org
Wordpress Learning Management SystemWordPress extension · Vibethemes

CVE-2025-53420

HIGH · 7.1 CVSS v3.1 Published 2025-10-22
Fix available
A fix is available. Upgrade to after 1.9.9.8 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in VibeThemes WPLMS wplms_plugin allows Reflected XSS.This issue affects WPLMS: from n/a through <= 1.9.9.8.

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 · high confidence

Reflected XSS vulnerability in the WPLMS WordPress plugin allows attackers to inject malicious scripts through unsanitized user input that gets reflected in web pages. The vulnerability exists in versions through 1.9.9.8 of the wplms_plugin.

MitigationApply output encoding and input validation/sanitization to all user-supplied parameters in the WPLMS plugin code, specifically focusing on the endpoint(s) where user input is reflected without proper escaping.

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
Affected:<= 1.9.9.8

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WPLMS plugin is installed
    Navigate to WordPress Admin > Plugins > Installed Plugins and look for 'Vibethemes Wordpress Learning Management System' or 'WPLMS', or inspect the /wp-content/plugins/ directory for a wplms folder
    Affected if The WPLMS plugin folder exists in the WordPress plugins directory
  2. Determine installed WPLMS version
    In WordPress Admin > Plugins, find the WPLMS plugin entry and read the version number displayed beneath the plugin name, or check the main plugin PHP file for the 'Version' header comment
    Affected if The installed version is 1.9.9.8 or lower
  3. Identify reflected input parameters
    Review the WPLMS plugin source code for PHP files that contain $_GET, $_POST, or $_REQUEST superglobals outputting to HTML without sanitization functions (such as esc_html, esc_attr, or wp_kses)
    Affected if Any parameter from user input is found being directly echoed or printed to output without encoding
  4. Test for reflected XSS manually
    Use browser developer tools or a proxy to submit common WPLMS URLs (course, member, or assignment pages) with a harmless test payload like <img src=x onerror=alert(1)> in URL parameters, and observe if the payload renders unescaped in the response
    Affected if The test payload appears literally in the HTML response without being escaped or removed
  5. Check web application firewall logs
    Review WAF, web server, or proxy logs for attempted XSS patterns targeting WPLMS endpoints, looking for requests with <script>, onerror=, or other XSS vectors in URL parameters
    Affected if Log entries show XSS injection attempts against WPLMS paths that were not blocked

If the WPLMS plugin version is 1.9.9.8 or lower and any user-supplied parameters are reflected in pages without sanitization, the environment is vulnerable to this reflected XSS.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.9.9.8
Interim mitigation

Apply output encoding and input validation/sanitization to all user-supplied parameters in the WPLMS plugin code, specifically focusing on the endpoint(s) where user input is reflected without proper escaping.

Fix this in Wordpress Learning Management System Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-53420 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-53420 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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