dbcve.org
Essential Real EstateWordPress extension · G5plus

CVE-2025-30849

CRITICAL · 9.8 CVSS v3.1 Published 2025-04-01
Fix available
A fix is available. Upgrade to 5.2.1 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
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in g5theme Essential Real Estate essential-real-estate allows PHP Local File Inclusion.This issue affects Essential Real Estate: from n/a through <= 5.2.0.

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

A PHP Local File Inclusion vulnerability in the Essential Real Estate theme (versions <= 5.2.0) allows remote attackers to include and execute arbitrary local files on the server via unsanitized input in include/require statements. The CVSS 9.8 indicates network exploitability with no authentication required, potentially enabling sensitive file disclosure or remote code execution.

MitigationUpdate to the latest patched version of Essential Real Estate theme. If no patch is available, implement strict input validation on all file inclusion parameters, use whitelist-based file validation, and ensure allow_url_include is disabled in PHP configuration.

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
Essential Real EstateWordPress extension
Affected:< 5.2.1

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. Identify the installed Essential Real Estate theme version
    Locate the theme's style.css file in wp-content/themes/essential-real-estate/ and check the 'Version:' header in the file comments. Alternatively, check version defined in functions.php or a dedicated version.php file.
    Affected if The reported version is 5.2.0 or lower, or if no version is displayed (older unversioned releases).
  2. Locate PHP include/require statements in the theme
    Search the theme directory for PHP files containing include(), require(), include_once(), or require_once() statements that use variables or request parameters without proper sanitization. Common patterns include: include($_GET['file']) or require($some_variable).
    Affected if Unsanitized file inclusion code that uses user-supplied input (GET, POST, or COOKIE parameters) is found in the theme files.
  3. Verify web accessibility of vulnerable parameters
    If the vulnerable code is found, test whether the affected parameters are accessible via HTTP requests to the website. For example, attempt a controlled request like: example.com/?page=../../../wp-config.php (using a safe test file first).
    Affected if The vulnerable parameter is directly accessible via URL without authentication and accepts path traversal sequences.
  4. Review PHP configuration settings
    Check the php.ini or phpinfo() output for the allow_url_include setting. Also verify if open_basedir restrictions are in place.
    Affected if allow_url_include is enabled (though this is primarily an LFI, not RFI, this setting can exacerbate the impact).

You are affected if the Essential Real Estate theme version is 5.2.0 or lower AND the theme contains unsanitized include/require statements that accept user input, which are accessible via web requests.

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

Update to the latest patched version of Essential Real Estate theme. If no patch is available, implement strict input validation on all file inclusion parameters, use whitelist-based file validation, and ensure allow_url_include is disabled in PHP configuration.

Recommended fix High confidence

5.2.1

  1. Backup your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate Essential Real Estate plugin and click 'Update now' or use WordPress update mechanism
  4. Alternatively, via WP-CLI run: wp plugin update essential-real-estate
  5. After update, verify the installed version shows 5.2.1
  6. Test that the real estate functionality works correctly on your site

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

Fix this in Essential Real Estate Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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