CVE-2025-4601
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 · uneditedThe "RH - Real Estate WordPress Theme" theme for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 4.4.0. This is due to the theme not properly restricting user roles that can be updated as part of the inspiry_update_profile() function. This makes it possible for authenticated attackers, with subscriber-level access and above, to set their role to that of an administrator. The vulnerability was partially patched in version 4.4.0, and fully patched in version 4.4.1.
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 confidenceThe RH - Real Estate WordPress Theme contains a privilege escalation vulnerability in the inspiry_update_profile() function. Authenticated users with subscriber-level access can manipulate their user role to administrator by sending a modified role parameter in profile update requests. The vulnerability was partially patched in version 4.4.0 and fully patched in version 4.4.1.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if RH - Real Estate theme is installedCheck the wp-content/themes directory for the rh-real-estate folder, or inspect the theme header in wp-content/themes/rh-real-estate/style.css for the Version fieldAffected if The theme folder rh-real-estate exists in the themes directory
-
Determine the installed theme versionRead the Version: x.x.x line from the theme header comment in style.cssAffected if The version number is 4.4.0 or lower (versions 4.4.1 and later contain the fix)
-
Verify the inspiry_update_profile function exists in the themeSearch theme PHP files (typically in inc/ or functions.php) for the string 'function inspiry_update_profile'Affected if The function is present in the theme code, making the vulnerable profile update feature available
-
Confirm WordPress user roles are configuredNavigate to WordPress admin Users > All Users and review the list of existing user accounts and their assigned rolesAffected if Any subscriber-level or low-privilege user accounts exist in the system who could send profile update requests
You are affected if the RH - Real Estate theme version is 4.4.0 or earlier and the inspiry_update_profile function is present with subscriber or other low-privilege user accounts accessible on the site.
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.
dbcve · scopedUpdate the RH - Real Estate WordPress Theme to version 4.4.1 or later to apply the complete patch for the privilege escalation vulnerability.
RH - Real Estate WordPress Theme version 4.4.1
- Update the RH - Real Estate WordPress Theme to version 4.4.1 or later
- Verify the update was successfully applied by checking the theme version in WordPress under Appearance > Themes
- Confirm that subscriber-level users can no longer modify their role to administrator through the inspiry_update_profile() function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-4601 — 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-4601 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