dbcve.org
Ere Recently ViewedWordPress extension · G5plus

CVE-2024-24797

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to 2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Deserialization of Untrusted Data vulnerability in G5Theme ERE Recently Viewed – Essential Real Estate Add-On.This issue affects ERE Recently Viewed – Essential Real Estate Add-On: from n/a through 1.3.

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

This is a deserialization of untrusted data vulnerability in the ERE Recently Viewed WordPress plugin. The plugin deserializes data from an untrusted source without proper validation, which could allow an unauthenticated attacker to craft malicious serialized payloads leading to code execution.

MitigationUpgrade to a patched version of the plugin that implements safe deserialization practices, input validation, or uses safer data formats like JSON instead of PHP serialization.

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
Ere Recently ViewedWordPress extension
Affected:< 2.0

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
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 checks

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

  1. Locate the plugin installation directory
    Navigate to your WordPress site's wp-content/plugins/ directory and look for a folder named 'ere-recently-viewed', 'g5plus-ere-recently-viewed', or similar naming convention containing 'recently viewed' in the folder name
    Affected if the plugin folder exists in the plugins directory
  2. Identify the installed version number
    Open the main plugin PHP file (usually named similarly to the folder or plugin-name.php) and look for the 'Version:' header comment in the file's plugin metadata, or check the readme.txt file for the 'Stable tag:' or 'Version:' entry
    Affected if the version found is below 2.0 (for example: 1.9, 1.8, 1.0, etc.)
  3. Confirm the plugin is active
    In the WordPress admin dashboard, go to Plugins > Installed Plugins and check whether the 'ERE Recently Viewed' or 'G5plus Ere Recently Viewed' plugin is activated
    Affected if the plugin is currently active on the site
  4. Verify vulnerable deserialization code exists
    If you have file access, search the plugin files for PHP unserialize() function calls that process data from external or user-controlled sources such as $_POST, $_GET, $_COOKIE, or AJAX request parameters
    Affected if unserialize() calls are present and processing untrusted input without prior sanitization or validation

Your site is affected if the ERE Recently Viewed plugin is installed with a version number less than 2.0 and the plugin files contain unsafe unserialize() calls processing untrusted data.

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 2.0 or later
Fixed in 2.0
Interim mitigation

Upgrade to a patched version of the plugin that implements safe deserialization practices, input validation, or uses safer data formats like JSON instead of PHP serialization.

Recommended fix High confidence

Version 2.0 or later

  1. 1. Backup your WordPress site database and files.
  2. 2. Navigate to WordPress admin dashboard > Plugins.
  3. 3. Locate the 'ERE Recently Viewed – Essential Real Estate Add-On' plugin.
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest version.
  5. 5. Alternatively, download version 2.0 or later from a trusted source and upload via Plugins > Add New > Upload Plugin.
  6. 6. After upgrade, verify the plugin is active and functioning correctly.
  7. 7. Test the 'Recently Viewed' functionality on the real estate site to ensure no regressions.
Caveat Review plugin settings and front-end display after upgrade as minor layout adjustments may be needed

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

Fix this in Ere Recently Viewed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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