CVE-2025-6934 in the critical feed json
Opal Estate Pro <= 1.7.5 - Unauthenticated Privilege Escalation via 'on_regiser_user'
published 2025-07-01 16 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-19602
- cvss
- 9.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 25.4%
- EPSS 25.4% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
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.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- total
- Assessed
- 16 mo ago
Exploit prediction
25.37% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template The Opal Estate Pro – Property Management <= 1.7.5 - Unauthenticated Privilege Escalation nuclei detection template
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected products
- wpopal Opal Estate Pro – Property Management and Submission
Classification
- Weakness
-
- CWE-269 Improper Privilege Management
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/5d7b75a4-67b4-4347-91a6-dbf98da5ceaf?source=cve
- themeforest.net /item/fullhouse-real-estate-responsive-wordpress-theme/16179481
- plugins.trac.wordpress.org /browser/opal-estate-pro/trunk/inc/user/class-opalestate-user.php#L228
- plugins.trac.wordpress.org /browser/opal-estate-pro/trunk/inc/user/class-opalestate-user.php#L235
Sources
- CVE List CVE-2025-6934
- NVD CVE-2025-6934
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.