CVE-2025-68072
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 · uneditedMissing Authorization vulnerability in Merv Barrett Easy Property Listings easy-property-listings allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Easy Property Listings: from n/a through <= 3.5.20.
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 confidenceThe Easy Property Listings WordPress plugin versions 3.5.20 and earlier contain a missing authorization vulnerability allowing attackers to exploit incorrectly configured access control security levels. This likely permits unauthenticated or unauthorized users to access functionality or data they should not have permission to view or modify.
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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Easy Property Listings plugin is installedLog into WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Easy Property Listings' in the list of active plugins.Affected if Plugin is installed and active
-
Determine the installed plugin versionIn the Plugins list, find Easy Property Listings and note the version number displayed beneath the plugin name. Alternatively, access the plugin file directly via FTP or file manager at wp-content/plugins/easy-property-listings/readme.txt and check the version header.Affected if Version is 3.5.20 or earlier
-
Identify exposed admin or frontend endpointsReview the site for publicly accessible plugin endpoints that may lack capability checks. Common locations include AJAX actions (wp-admin/admin-ajax.php with action parameter matching EPL hooks), REST API routes under wp-json/epl/v1/, or direct PHP files in the plugin directory. Use a network scanner or review plugin source code for functions hooked to admin_init, init, or wp_ajax_ without capability checks.Affected if Any EPL-related endpoints or actions are accessible to unauthenticated users without proper permission checks
-
Check WordPress user role configurationNavigate to Users > Roles in WordPress admin or inspect user capabilities using a role editor plugin. Verify if any custom EPL capabilities (such as epl_manage_settings or epl_access_admin) have been improperly assigned to subscriber or subscriber-level roles.Affected if Subscriber or unauthenticated users have elevated capabilities or access to EPL admin functions
If Easy Property Listings version 3.5.20 or earlier is installed and any plugin functionality is accessible to unauthorized users, the environment is affected by this missing authorization vulnerability.
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 dataUpdate to the latest version of Easy Property Listings if a patch is available. If no patch exists, review and enforce proper capability checks and role-based access controls on all sensitive plugin functions.
- Consultation2.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-68072 — 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-2025-68072 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