CVE-2024-4273
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 Essential Real Estate plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's 'ere_property_map' shortcode in all versions up to, and including, 4.4.2 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 Essential Real Estate WordPress plugin is vulnerable to stored XSS via the 'ere_property_map' shortcode. Authenticated attackers with contributor-level access can inject malicious JavaScript through unsanitized shortcode attributes that are not properly escaped when output, causing scripts to execute when pages containing the shortcode are accessed.
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.3CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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.
-
Verify Essential Real Estate plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Essential Real Estate' by G5plus, or check the wp-content/plugins directory for the essential-real-estate folderAffected if The plugin is present in the installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins, find Essential Real Estate, and note the version number displayed, or read the main plugin file header for the Version fieldAffected if Version is lower than 4.4.3 (for example, 4.4.2, 4.4.1, etc.)
-
Identify pages using the ere_property_map shortcodeSearch the WordPress database or use a search tool to find all posts, pages, and custom post types containing the [ere_property_map] shortcode. Check wp_postmeta and wp_posts tables for this shortcode stringAffected if The shortcode is present in any published content
-
Inspect shortcode attributes for malicious contentFor each instance of [ere_property_map] found, examine the attributes (such as map_center, zoom, height, etc.) for any unusual characters, script tags, event handlers (onclick, onerror, etc.), or encoded JavaScript payloadsAffected if Any shortcode contains unsanitized user-supplied attributes that could execute JavaScript when the page loads
-
Review contributor-level user accountsIn WordPress admin, go to Users and filter by the Contributor role. Identify how many contributor accounts exist and whether any are unauthorized or compromisedAffected if There are contributor users who could potentially author content with malicious shortcodes
The environment is affected if Essential Real Estate plugin version is below 4.4.3 AND the ere_property_map shortcode is in use with exploitable attributes, especially when contributor-level access exists.
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.3
Update the plugin to version 4.4.3 or later which implements proper input sanitization and output escaping on shortcode attributes. Until then, restrict contributor-level access or audit existing pages for malicious shortcode usage.
4.4.3
- Backup your WordPress site before making any changes
- Navigate to WordPress admin dashboard > Plugins > Installed Plugins
- Find 'Essential Real Estate' in the plugin list
- Click 'Update now' when an update to version 4.4.3 is available, or manually upload version 4.4.3 of the plugin
- After updating, verify the plugin shows version 4.4.3 under Plugins > Installed Plugins
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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 $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-4273 — 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-2024-4273 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