dbcve.org
RealhomesWordPress extension · Inspirythemes

CVE-2023-37885

HIGH · 8.8 CVSS v3.1 Published 2024-03-25
Fix available
A fix is available. Upgrade to 4.3.8 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Missing Authorization vulnerability in InspiryThemes RealHomes.This issue affects RealHomes: from n/a through 4.0.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

Missing Authorization vulnerability in InspiryThemes RealHomes theme version 4.0.2 and prior allows unauthenticated or unauthorized users to access functionality they should not have access to.

MitigationImplement proper authorization checks across all sensitive functions and administrative endpoints in the RealHomes theme.

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
RealhomesWordPress extension
Affected:< 4.3.8

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm RealHomes theme is installed
    Check your WordPress installation for the RealHomes theme by looking in wp-content/themes/ for a folder named 'realhomes' or by viewing the theme in WordPress admin under Appearance > Themes
    Affected if The RealHomes theme folder exists in the themes directory
  2. Identify installed theme version
    Locate the style.css file in the realhomes theme folder and find the 'Version:' declaration in the file header, or check the version displayed in WordPress admin under Appearance > Themes > RealHomes theme details
    Affected if The version number displayed is lower than 4.3.8 (for example, 4.0.2, 4.0.0, 3.x.x, etc.)
  3. Verify authorization on sensitive endpoints
    Review the theme's admin functionality and sensitive features. Test accessing administrative endpoints or sensitive functions without proper authentication or authorization tokens to determine if access controls are enforced
    Affected if Unauthenticated or unauthorized users can access admin functions, settings, or sensitive data that should require authorization
  4. Check for unauthenticated API exposure
    Examine theme AJAX actions and public endpoints defined in the theme. Look for functions hooked to wp_ajax_ or wp_ajax_nopriv_ that perform sensitive operations without verifying user permissions
    Affected if The theme exposes AJAX or other endpoints that perform privileged operations without checking if the user has appropriate authorization

You are affected if the RealHomes theme version is below 4.3.8 AND the theme exposes administrative or sensitive functionality without proper authorization checks.

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
Upgrade available Upgrade to 4.3.8 or later
Fixed in 4.3.8
Interim mitigation

Implement proper authorization checks across all sensitive functions and administrative endpoints in the RealHomes theme.

Recommended fix High confidence

RealHomes version 4.3.8 or later

  1. 1. Backup your WordPress site before performing any updates.
  2. 2. Navigate to Appearance > Themes in your WordPress admin dashboard.
  3. 3. Update the RealHomes theme to version 4.3.8 or later.
  4. 4. Verify the update was successful by checking the theme version in Appearance > Themes.

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

Fix this in Realhomes Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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