CVE-2025-66088
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 Property Hive PropertyHive propertyhive allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects PropertyHive: from n/a through <= 2.1.12.
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 confidenceThis is a missing authorization (IDOR or broken access control) vulnerability in the PropertyHive WordPress plugin. The plugin fails to properly verify user permissions before allowing access to certain functionality or data, allowing unauthenticated or lower-privileged users to perform actions intended for higher-privilege roles due to incorrectly configured access control security levels.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 PropertyHive plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for PropertyHive in the list. Alternatively, check /wp-content/plugins/ for a folder named 'propertyhive' or similar.Affected if PropertyHive plugin is present in the WordPress installation
-
Determine installed PropertyHive versionIn WordPress admin > Plugins, find PropertyHive and view the version number under the plugin name. Or check the main plugin file header in /wp-content/plugins/[propertyhive-folder]/propertyhive.php for 'Version:' comment.Affected if Version is at or below the vulnerable release (compare to patched version when available)
-
Confirm plugin is activeIn WordPress admin > Plugins, verify PropertyHive shows as 'Active' under the plugin status column.Affected if Plugin is active and handling property data or user actions
-
Identify exposed sensitive endpointsAudit WordPress site for PropertyHive REST API endpoints or admin AJAX actions by reviewing plugin code in /wp-content/plugins/[propertyhive-folder]/includes/ directories. Look for functions handling property listings, applicant data, or role-based actions without current_user_can() checks.Affected if Unauthenticated or subscriber-level users can access endpoints that should require agent, manager, or administrator privileges
User is affected if PropertyHive plugin is installed, active, and running a version lacking the authorization patch, allowing privilege escalation via accessible sensitive endpoints.
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 PropertyHive to the latest version containing the security patch. If no patch is available, audit all endpoints and functions that handle sensitive property data and role-based actions to implement proper capability checks using WordPress current_user_can() or role verification.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-66088 — 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-66088 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