CVE-2025-49867
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 · uneditedIncorrect Privilege Assignment vulnerability in InspiryThemes RealHomes realhomes allows Privilege Escalation.This issue affects RealHomes: from n/a through <= 4.4.0.
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 privilege escalation vulnerability in the RealHomes WordPress theme where incorrect privilege assignment allows authenticated users to gain elevated permissions beyond what their assigned role should permit. The vulnerability exists in versions up to and including 4.4.0.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 4.4.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed RealHomes theme versionNavigate to Appearance > Themes in the WordPress admin dashboard and locate the RealHomes theme. The version number is displayed in the theme details panel. Alternatively, check the style.css file in the theme directory for the 'Version:' header comment.Affected if The installed version is below 4.4.1 (e.g., 4.4.0, 4.3.x, or any version up to and including 4.4.0)
-
Verify if WordPress user registration is enabledGo to Settings > General in the WordPress admin and locate the 'Membership' setting. Check if the option 'Anyone can register' is checked.Affected if User registration is enabled and the RealHomes version is vulnerable, allowing newly registered users to potentially exploit the privilege escalation flaw
-
Review existing user roles and capabilitiesNavigate to Users > All Users in the WordPress admin. Examine the assigned role for each user account. Pay particular attention to any users registered through the site who may have elevated roles beyond what they should legitimately possess.Affected if Users with unexpected elevated roles (such as Administrator, Editor, or Author) exist that should not have those permissions based on the site's intended access model
-
Check for custom role assignments via RealHomes functionalityInspect the WordPress database tables related to user capabilities, specifically any custom role mappings that the RealHomes theme may create. Look in the wp_options table for theme-specific user role configurations.Affected if Custom role assignments or capability modifications created by the theme are present, which could indicate the vulnerable privilege assignment mechanism is in use
The environment is affected if the RealHomes theme version is below 4.4.1 and user registration is enabled, allowing authenticated users to potentially gain elevated permissions beyond their assigned role.
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 · scoped4.4.1
Update to the latest version of RealHomes theme when a patch is released by InspiryThemes. Until then, limit user registration and carefully audit existing user accounts with elevated roles.
RealHomes 4.4.1
- 1. Backup your WordPress site and database before making any changes.
- 2. Navigate to your WordPress dashboard > Appearance > Themes.
- 3. Deactivate the current RealHomes theme.
- 4. Download RealHomes version 4.4.1 or later from the official InspiryThemes source or your account on their website.
- 5. Upload and activate the new version 4.4.1 of the RealHomes theme.
- 6. Verify the theme version in Appearance > Themes to confirm 4.4.1 is installed.
- 7. Test critical functionality (property submissions, user registrations, admin access) to ensure the site operates normally.
- 8. Check for any child theme customizations and ensure they are compatible with the new version.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-49867 — 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-49867 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