dbcve.org
Incorrect Privilege AssignmentWeakness · CWE-266

CVE-2025-39459

HIGH · 7.3 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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
Incorrect Privilege Assignment vulnerability in contempoinc Real Estate 7 realestate-7 allows Privilege Escalation.This issue affects Real Estate 7: from n/a through <= 3.5.2.

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 confidence

The Real Estate 7 WordPress theme by contempoinc has an Incorrect Privilege Assignment vulnerability allowing privilege escalation. This indicates the application improperly assigns or enforces user role permissions, enabling a lower-privileged user (such as a subscriber or guest) to perform actions reserved for administrators or higher-privileged roles.

MitigationUpdate to the latest version of Real Estate 7 (if a patch is available) and audit user role capabilities to ensure proper access controls are enforced across all administrative functions.

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
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

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 if Real Estate 7 theme is active
    Navigate to wp-admin/themes.php or check wp-content/themes/ directory for the realestate-7 folder. Verify if it is the currently active theme.
    Affected if Real Estate 7 theme by contempoinc is installed and activated on the WordPress site
  2. Determine the installed theme version
    Open the theme's style.css file in wp-content/themes/realestate-7/ and locate the 'Version:' header in the file comments, or check version information in the theme's functions.php
    Affected if The installed version matches or falls within an affected range (prior to any patch release)
  3. Audit user roles for unexpected privileges
    Use a user role editor plugin or query the wp_usermeta table to list all users and their assigned capabilities. Look for subscribers, contributors, or authors with capabilities typically reserved for administrators (like manage_options, edit_users, delete_users).
    Affected if Any user with a role of subscriber, contributor, or author possesses administrative-level capabilities or can perform administrative actions
  4. Check for unauthorized administrator accounts
    Navigate to Users > All Users in wp-admin and review the list. Identify any administrator accounts that were not created by known admins, or query wp_users and wp_usermeta for user_level 10 or capability 'administrator' assigned to unexpected user IDs.
    Affected if There exist administrator accounts not created by legitimate site administrators, or the total number of admins exceeds expected
  5. Verify capability enforcement on sensitive actions
    Attempt to access or inspect AJAX actions or admin endpoints that the Real Estate 7 theme provides (common paths: wp-admin/admin-ajax.php?action=realestate_*, or theme-specific AJAX handlers). Use a role testing plugin to confirm low-privileged users cannot access these endpoints.
    Affected if Users with subscriber or contributor roles can successfully execute theme AJAX handlers or admin functions that should require administrator privileges

The site is affected if Real Estate 7 theme is active AND low-privileged users have administrative capabilities or can perform admin-level actions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of Real Estate 7 (if a patch is available) and audit user role capabilities to ensure proper access controls are enforced across all administrative functions.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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