dbcve.org
RealtyWordPress extension · Bestwebsoft

CVE-2017-18532

MEDIUM · 6.1 CVSS v3.0 Published 2019-08-20
Fix available
A fix is available. Upgrade to 1.1.0 or later.
See remediation →
68/100
Remediation priority · Elevated
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
The realty plugin before 1.1.0 for WordPress has multiple XSS issues.

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

The realty WordPress plugin before version 1.1.0 contains multiple Cross-Site Scripting (XSS) vulnerabilities. XSS allows attackers to inject malicious scripts into web pages viewed by other users, potentially stealing session cookies, credentials, or performing actions on behalf of victims.

MitigationUpdate the realty plugin to version 1.1.0 or later. If no update is available, consider removing the plugin until a patched version is released, as XSS vulnerabilities can be exploited via malicious links or form submissions.

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
RealtyWordPress extension
Affected:< 1.1.0

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
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 the Realty plugin is installed
    Log into WordPress admin panel and navigate to Plugins > Installed Plugins, or check the /wp-content/plugins/ directory for a folder named 'realty' or 'bestwebsoft-realty'
    Affected if The realty plugin folder exists in the WordPress plugins directory
  2. Identify the installed plugin version
    In WordPress admin, click on the Realty plugin to view its details and version number, or open the plugin's main PHP file (e.g., realty.php) and look for the 'Version' header comment at the top
    Affected if The displayed version number is lower than 1.1.0 (e.g., 1.0.9, 1.0.8, etc.)
  3. Confirm the plugin is active
    In WordPress admin under Plugins > Installed Plugins, verify that the Realty plugin shows as 'Active' rather than 'Inactive'
    Affected if The plugin status shows as Active and the version is below 1.1.0

If the Bestwebsoft Realty plugin is installed and active with a version lower than 1.1.0, the environment is affected by this CVE.

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 1.1.0 or later
Fixed in 1.1.0
Interim mitigation

Update the realty plugin to version 1.1.0 or later. If no update is available, consider removing the plugin until a patched version is released, as XSS vulnerabilities can be exploited via malicious links or form submissions.

Fix this in Realty Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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