CVE-2026-1845
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 Real Estate Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via admin settings in all versions up to, and including, 1.0.9 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with administrator-level permissions and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. This only affects multi-site installations and installations where unfiltered_html has been disabled.
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 Real Estate Pro WordPress plugin (versions up to 1.0.9) contains a Stored XSS vulnerability in admin settings due to insufficient input sanitization and output escaping. Authenticated attackers with administrator-level permissions can inject malicious scripts that execute when users access affected pages. This only impacts multi-site WordPress installations or sites where unfiltered_html is disabled.
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
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
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.
-
Confirm WordPress multi-site statusCheck your WordPress configuration by looking for 'MULTISITE' defined as true in wp-config.php, or check the Sites menu in the network admin dashboard.Affected if WordPress is configured as a multi-site (network) installation - this condition makes the site vulnerable regardless of other settings.
-
Check unfiltered_html capabilityAs an administrator, go to Users > All Users and edit a user profile. Look for the 'unfiltered_html' capability in the user roles, or use a plugin/network admin query to check if unfiltered_html is disabled for all users.Affected if unfiltered_html is disabled for your user roles - this condition makes single-site installations vulnerable.
-
Verify Real Estate Pro plugin versionIn WordPress admin, go to Plugins > Installed Plugins and look for 'Real Estate Pro' in the list. The version number is displayed below the plugin name.Affected if The installed version is 1.0.9 or earlier.
-
Identify administrator access pointsReview all user accounts with Administrator role in Users > All Users. Check if any administrators were added recently or have unexpected credentials.Affected if There are untrusted or compromised administrator accounts that could have injected malicious scripts.
Your environment is affected if you run Real Estate Pro plugin version 1.0.9 or earlier AND either have a multi-site WordPress installation OR have unfiltered_html disabled.
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.
From vendor dataUpdate to a patched version of the plugin once available; otherwise, ensure unfiltered_html is enabled and restrict administrator access to trusted users only. For multi-site installations, review and harden network settings.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1845 — 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-2026-1845 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