dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-62043

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable

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 WPSight WPCasa allows DOM-Based XSS.This issue affects WPCasa: from n/a through 1.4.1.

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 confidence

DOM-Based Cross-Site Scripting (XSS) vulnerability in WPSight WPCasa WordPress plugin versions through 1.4.1. The vulnerability allows malicious JavaScript to be injected via unsanitized user input that gets processed by client-side JavaScript and reflected in the DOM without proper output encoding.

MitigationUpgrade WPCasa to the latest version that includes proper input sanitization and output encoding. Until a patch is available, implement Web Application Firewall (WAF) rules to block XSS attack patterns and disable or restrict the affected plugin functionality.

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 checks

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

  1. Verify WPCasa plugin is installed
    Check the WordPress plugins directory at wp-content/plugins/ or view the Installed Plugins page in the WordPress admin dashboard for the WPCasa or WPSight WPCasa plugin entry
    Affected if The WPCasa plugin appears in the installed plugins list
  2. Identify installed WPCasa version
    Navigate to WordPress Admin > Plugins > Installed Plugins and locate the WPCasa plugin to view its version number, or inspect the plugin main file header in wp-content/plugins/wpcasa/includes/class-wpcasa.php
    Affected if The installed version is 1.4.1 or any version prior to 1.4.1 (e.g., 1.4.0, 1.3.x, etc.)
  3. Identify client-side input handling features
    Inspect the plugin JavaScript files in wp-content/plugins/wpcasa/assets/js/ for functions that process user input and modify the DOM (search forms, listing filters, or dynamic content loaders)
    Affected if The plugin contains JavaScript that takes user input and inserts it directly into the DOM without encoding (e.g., using innerHTML, document.write, or direct DOM manipulation of user-supplied values)
  4. Check for active search or filter functionality
    Visit the frontend of the WordPress site and test any property search, listing filter, or user input forms provided by WPCasa. Inspect browser developer tools (Elements panel) to see if submitted input values appear in the DOM as-is
    Affected if User-supplied input is reflected in the page HTML/DOM without being escaped or encoded (visible as raw input in the DOM)

You are affected if the WPCasa plugin version is 1.4.1 or earlier and any client-side features that accept user input and reflect it into the DOM are actively used on the site.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WPCasa to the latest version that includes proper input sanitization and output encoding. Until a patch is available, implement Web Application Firewall (WAF) rules to block XSS attack patterns and disable or restrict the affected plugin functionality.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-62043 — 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-62043 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