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

CVE-2026-57381

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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 Property Hive PropertyHive propertyhive allows Reflected XSS.This issue affects PropertyHive: from n/a through <= 2.2.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 confidence

Reflected XSS vulnerability in PropertyHive WordPress plugin (versions <= 2.2.3) allows attackers to inject malicious scripts through unsanitized user input that gets reflected back in web pages without proper output encoding.

MitigationUpdate PropertyHive to the latest patched version. Until then, implement output encoding and input validation on all user-supplied parameters in the plugin.

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 checks

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

  1. Verify PropertyHive plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for PropertyHive in the list. Alternatively, check the /wp-content/plugins/ directory for a propertyhive folder.
    Affected if PropertyHive plugin is present on the WordPress site
  2. Determine installed PropertyHive version
    In WordPress admin, go to Plugins > Installed Plugins, find PropertyHive, and note the version number displayed. If not visible in the list, check the plugin's main PHP file header for the Version field.
    Affected if Installed version is 2.2.3 or lower
  3. Identify user input parameters used by the plugin
    Review plugin settings and frontend forms where users submit data (such as property search forms, contact forms, or inquiry fields). Common XSS entry points include query string parameters in URLs served by the plugin.
    Affected if The plugin processes and reflects user-supplied parameters in page output without encoding
  4. Check for output encoding on reflected parameters
    Inspect page source code where user input is echoed back. Use browser dev tools or view source to examine if special characters like < > " ' are HTML-encoded (&lt; &gt; &quot; &#x27;) or appear raw.
    Affected if User input appears unencoded in HTML output (raw <script> tags, unescaped quotes, or raw < characters)

A site is affected if it runs PropertyHive plugin version 2.2.3 or lower and displays unencoded user input on any page.

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

Update PropertyHive to the latest patched version. Until then, implement output encoding and input validation on all user-supplied parameters in the plugin.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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