Easy Property ListingsWordPress extension · Realestateconnected
CVE-2020-5530
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 · uneditedCross-site request forgery (CSRF) vulnerability in Easy Property Listings versions prior to 3.4 allows remote attackers to hijack the authentication of administrators via unspecified vectors.
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 · high confidenceCross-site request forgery (CSRF) vulnerability in Easy Property Listings WordPress plugin versions prior to 3.4 allows remote attackers to trick authenticated administrators into executing unintended administrative actions by leveraging the lack of anti-CSRF tokens in plugin forms or admin actions.
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
< 3.4CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Easy Property Listings plugin is installedNavigate to WordPress Admin > Plugins and confirm 'Easy Property Listings' or 'Realestateconnected Easy Property Listings' appears in the installed plugins list, or check the wp-content/plugins/ directory for the easy-property-listings folder.Affected if Plugin folder exists in wp-content/plugins/
-
Check installed plugin versionIn WordPress Admin > Plugins, click on the plugin name to view the version details, or open the main plugin file (usually easy-property-listings.php) and locate the 'Version:' header in the plugin comments.Affected if Unable to determine version or version displayed is below 3.4
-
Compare version against affected rangeIf version is visible, compare it to the affected range: any version prior to 3.4 (such as 3.3.x, 3.2.x, 3.1.x, 3.0.x, 2.x.x, etc.) is affected.Affected if Installed version number is less than 3.4 (e.g., 3.3.9, 3.2.0, etc.)
-
Confirm plugin is active with admin accessIn WordPress Admin > Plugins, verify the plugin shows as 'Active' and that you have administrator-level access to the WordPress site.Affected if Plugin is active AND you have administrator privileges, making you a potential target for CSRF attacks via the plugin forms
You are affected if the Easy Property Listings plugin is installed and active with a version number lower than 3.4.
Generated from the published advisory. Verify against your own configuration.
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 data3.4
Update Easy Property Listings plugin to version 3.4 or later, which includes CSRF protection. As a defense-in-depth measure, ensure WordPress nonce verification is implemented for all admin-area actions.
Fix this in Easy Property Listings
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5530 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-5530 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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