dbcve.org
Easy Property ListingsWordPress extension · Realestateconnected

CVE-2024-32799

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-09
Fix available
A fix is available. Upgrade to 3.5.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
Missing Authorization vulnerability in Merv Barrett Easy Property Listings.This issue affects Easy Property Listings: from n/a through 3.5.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

Missing Authorization vulnerability in the Easy Property Listings WordPress plugin allows unauthenticated attackers to access sensitive functionality or data without proper permission checks. The critical CVSS 9.8 score indicates the flaw is easily exploitable and can lead to complete system compromise.

MitigationUpdate Easy Property Listings to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Implement web application firewall rules to block suspicious requests to plugin endpoints.

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
Easy Property ListingsWordPress extension
Affected:< 3.5.4

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Check if Easy Property Listings plugin is installed
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, and search for 'Easy Property Listings' or 'Realestateconnected Easy Property Listings' in the plugin list
    Affected if The plugin is not found in the installed plugins list - then they are NOT affected
  2. Identify the installed plugin version
    In the WordPress admin Plugins page, locate Easy Property Listings and view the plugin details to find the version number displayed under the plugin name
    Affected if The displayed version number is less than 3.5.4 (for example 3.5.3, 3.5.2, etc.) - they ARE affected
  3. Verify plugin files exist via file system
    If filesystem access is available, check the plugin directory at wp-content/plugins/easy-property-listings/ and locate the main plugin file (usually easy-property-listings.php) to read the version defined in the plugin header comments
    Affected if The version defined in the plugin header comment is less than 3.5.4 - they ARE affected
  4. Check for unauthorized access indicators
    Review WordPress access logs for requests to plugin AJAX endpoints or admin-ajax.php that originate from unauthenticated IP addresses targeting easy-property-listings functionality
    Affected if Unauthenticated requests are observed hitting plugin-specific endpoints - this indicates active exploitation of the authorization flaw

The environment is affected if Easy Property Listings plugin is installed with a version number below 3.5.4, as this missing authorization vulnerability allows unauthenticated access to sensitive plugin functionality.

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.

dbcve · scoped
Upgrade available Upgrade to 3.5.4 or later
Fixed in 3.5.4
Interim mitigation

Update Easy Property Listings to the latest version immediately. If no patch is available, disable the plugin until a fix is released. Implement web application firewall rules to block suspicious requests to plugin endpoints.

Recommended fix High confidence

3.5.4

  1. 1. Create a full backup of your WordPress site including database and files
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Locate Easy Property Listings plugin
  4. 4. Click Update Now or update directly from the Plugins page
  5. 5. Verify the plugin version shows 3.5.4 after update
  6. 6. Test that listings, property data, and admin functionality work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Easy Property Listings Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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