CVE-2023-37886 is a medium severity (CVSS 5.4) missing authorization flaw in the RealHomes theme from InspiryThemes, through version 4.0.2. A low privilege logged in user can reach functionality that is not properly restricted, with limited integrity and availability impact. Update the theme and confirm the fixed release with the vendor.
What's affected
The NVD record lists RealHomes as affected "from n/a through 4.0.2", which is Patchstack wording for every release up to and including 4.0.2. The record scores the flaw 5.4 with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L. The weakness is tracked as CWE-862 (missing authorization).
The vector is a network attack needing a low privilege account and no user interaction, with low integrity (I:L) and low availability (A:L) impact. It is a second, separate access control report against the same theme range as CVE-2023-37885, which scores 4.3, so check both records when you review your exposure.
The record names no fixed version, and the Patchstack page it links to could not be retrieved when we reviewed it (Patchstack blocked our request). The CVE is not flagged in CISA KEV in the record, and nothing we read says it is exploited in the wild. For the fixed release, check the vendor changelog or the Patchstack entry.
How to check if you're exposed
If you run WP-CLI, list the installed version and status of the theme:
wp theme list --fields=name,version,status,update
Look for RealHomes in the output. Anything at 4.0.2 or lower is in the affected range. In the dashboard the same information is under Appearance, Themes. On a fleet of sites, run the command per site or through your management tool, and include staging and forgotten test copies.
You can also check your dependency manifests and images. A free in-browser scan at gold.safeguard.sh/scan takes a package.json, a requirements.txt or an SBOM and shows known CVEs, though WordPress plugins are usually tracked by the CMS rather than a package manager, so keep a separate list of them.
What to do now
- List every WordPress site you run and note whether RealHomes is installed and at what version.
- Update RealHomes to the newest release the vendor offers. If the update is behind a license, renew it or plan the change, because the old version stays vulnerable.
- If you cannot update today, deactivate the theme on sites where it is not needed, or restrict access to the affected features with a web application firewall rule from your provider.
- Review user accounts and recent changes on any site that ran the affected version for a while, and remove accounts you do not recognise.
- Add the theme to a watch list so the next advisory reaches you the day it is published.
Why it matters
The pattern is a function that does its job for any logged in caller. The theme author needs to add a capability check or a nonce check where the request is handled. The record does not say which function is involved, and we do not guess.
The practical risk depends on who can log in to your site. If registration is open or you have many agent or customer accounts, a low privilege requirement is easy to meet. If only staff can log in, the exposure is much smaller, but you still want the update.
Quick check
Does updating RealHomes fully fix this?
The vendor decides that, and the record does not name a fixed version. Update to the latest release, read the changelog and the Patchstack entry, and confirm the version number afterwards.
Is this being exploited?
The record does not flag CVE-2023-37886 as a CISA KEV entry, and the sources we could read do not report exploitation. That can change, so keep the theme updated.
Sources
- Patchstack entry (linked from the NVD record; it could not be retrieved when we reviewed it)
- CVE-2023-37886 on Gold
Last reviewed: 19 October 2026.
