LiveActive security incident?Get immediate response
CVE Record

CVE-2019-15817: The easy-property-listings plugin before 3.4 for WordPress has XSS.

The easy-property-listings plugin before 3.4 for WordPress has XSS.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2019-15817 is a cross-site scripting issue in the Easy Property Listings WordPress plugin before version 3.4. Affected sites could expose administrators or users to injected script content. The source bundle does not provide severity, attack prerequisites, or impact details.

Executive priority

Treat as a targeted hygiene item for WordPress estates, especially public real-estate sites. Prioritize remediation where the plugin is internet-facing or accessible to untrusted users, but urgency is constrained by missing severity and exploit evidence.

Technical view

The public CVE description states that Easy Property Listings for WordPress before 3.4 has XSS. No CVSS vector, CWE, vulnerable parameter, authentication requirement, or proof-of-concept details are included in the provided sources.

Likely exposure

Exposure is likely limited to WordPress sites that installed Easy Property Listings before version 3.4. The bundle’s structured affected-product fields are incomplete, so confirm against plugin inventory and vendor records.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source in the bundle states active exploitation, so active exploitation should not be assumed.

Researcher notes

The bundle provides only a concise XSS description and references. It lacks vulnerable endpoint, parameter, role requirement, CVSS, and CWE data. Validate details against WPVulnDB and the WordPress plugin developer changelog before assigning severity.

Mitigation direction

  • Inventory WordPress sites for Easy Property Listings installations.
  • Upgrade Easy Property Listings to version 3.4 or later after checking vendor guidance.
  • Disable the plugin temporarily if it cannot be updated promptly.
  • Review plugin changelog and WPVulnDB entry for vendor-specific remediation details.

Validation and detection

  • Confirm each WordPress site is not running Easy Property Listings before 3.4.
  • Check WordPress admin plugin inventory and deployment records.
  • Review exposed property listing pages for unexpected script content indicators.
  • Verify vulnerability scanners map findings to CVE-2019-15817 and plugin version evidence.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-15817 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.