dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-6934

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The Opal Estate Pro – Property Management and Submission plugin for WordPress, used by the FullHouse - Real Estate Responsive WordPress Theme, is vulnerable to privilege escalation via in all versions up to, and including, 1.7.5. This is due to a lack of role restriction during registration in the 'on_regiser_user' function. This makes it possible for unauthenticated attackers to arbitrarily choose the role, including the Administrator role, assigned when registering.

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 confidence

The Opal Estate Pro WordPress plugin has a privilege escalation vulnerability in its user registration function 'on_register_user'. The function fails to restrict or validate the role parameter during registration, allowing unauthenticated attackers to specify any role including Administrator when creating a new user account.

MitigationUpdate the Opal Estate Pro plugin to version 1.7.6 or later. If no update is available, temporarily disable user registration functionality and audit existing user accounts for unauthorized administrator accounts created after the vulnerability disclosure date.

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
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. Identify plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Opal Estate Pro'. Check the version number displayed under the plugin name. Alternatively, check the plugin files: /wp-content/plugins/opal-estate-pro/readme.txt for the Version line, or /wp-content/plugins/opal-estate-pro/opal-estate-pro.php for the version constant.
    Affected if The plugin is installed and the version is earlier than 1.7.6 (e.g., 1.7.5, 1.7.4, etc.) or the version cannot be determined.
  2. Verify WordPress user registration is enabled
    In WordPress admin, go to Settings > General > Membership section and check 'Anyone can register' is ticked. Alternatively, check the wp_options table for 'users_can_register' value set to 1.
    Affected if WordPress user registration is enabled on the site.
  3. Review user accounts for suspicious administrator roles
    In WordPress admin, go to Users > All Users and examine the list for administrator accounts you did not create. Cross-reference the 'Registered' date with when the plugin was active. Check wp_users table for user_login and user_email that are unfamiliar.
    Affected if There are administrator accounts you did not create, especially registered during the time the plugin was active.
  4. Inspect recent user registration activity
    Check the wp_users and wp_usermeta tables for newly created accounts. Look for registrations that occurred recently or in batches. Query: SELECT user_login, user_registered, meta_key, meta_value FROM wp_users JOIN wp_usermeta ON wp_users.ID = wp_usermeta.user_id WHERE meta_key = 'wp_capabilities' AND meta_value LIKE '%administrator%' ORDER BY user_registered DESC.
    Affected if There are recent user registrations with administrator role that correspond to the time window the vulnerable plugin was installed.

Your environment is affected if Opal Estate Pro plugin is installed with a version below 1.7.6 AND WordPress user registration is enabled, allowing potential unauthorized admin account creation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Opal Estate Pro plugin to version 1.7.6 or later. If no update is available, temporarily disable user registration functionality and audit existing user accounts for unauthorized administrator accounts created after the vulnerability disclosure date.

Recommended fix Moderate confidence

Latest version of Opal Estate Pro plugin (version higher than 1.7.5) - check for 1.7.6 or subsequent release

  1. 1. Check WordPress admin dashboard > Plugins for any available updates to the Opal Estate Pro plugin
  2. 2. If an update is available, update to the latest version which should contain the fix for CVE-2025-6934
  3. 3. If no update is available from the WordPress repository, check the official vendor channels (ThemeForest or vendor website) for the patched version
  4. 4. After updating, verify that newly registered users can only be assigned roles lower than Administrator (e.g., Subscriber or Editor)
  5. 5. Audit existing user accounts to ensure no unauthorized Administrator accounts were created
  6. 6. Consider implementing additional server-side validation to restrict the 'role' parameter during user registration as a defense-in-depth measure

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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