dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-30793

HIGH · 7.5 CVSS v3.1 Published 2025-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in Property Hive Houzez Property Feed houzez-property-feed allows Path Traversal.This issue affects Houzez Property Feed: from n/a through <= 2.5.4.

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 Path Traversal vulnerability exists in the Houzez Property Feed WordPress plugin (versions <= 2.5.4) that allows attackers to access files outside the restricted web directory by manipulating file paths using '../' sequences. This could enable unauthorized reading or manipulation of sensitive filesystem resources.

MitigationUpgrade to a patched version of Houzez Property Feed that includes proper path validation and sanitization to prevent directory traversal attacks. If no patch is available, implement web server-level restrictions and input validation as a temporary measure.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Verify Houzez Property Feed plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Houzez Property Feed' in the list. Alternatively, check if the directory /wp-content/plugins/houzez-property-feed/ exists on the server.
    Affected if The plugin is installed and active
  2. Check installed plugin version
    In WordPress admin_plugins list, find Houzez Property Feed and note the version number displayed. Alternatively, inspect the main plugin file header in /wp-content/plugins/houzez-property-feed/houzez-property-feed.php for the 'Version' tag.
    Affected if Version is 2.5.4 or lower
  3. Identify if file import/export functionality is enabled
    Check the plugin settings pages under Houzez Property Feed menu in WordPress admin. Look for any import, export, CSV upload, or property sync features that handle file paths.
    Affected if Any file-based import/export or sync feature is configured and active
  4. Test for accessible endpoint accepting file paths
    Review plugin PHP files for functions handling file paths, particularly looking for file_get_contents, fopen, include, or similar file operations that might accept user-supplied paths. Check for any AJAX actions or public-facing endpoints.
    Affected if The plugin exposes any endpoint or functionality that accepts file path parameters without sanitization

You are affected if Houzez Property Feed plugin is installed with version 2.5.4 or lower AND any file-related feature that processes external paths is enabled or accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Houzez Property Feed that includes proper path validation and sanitization to prevent directory traversal attacks. If no patch is available, implement web server-level restrictions and input validation as a temporary measure.

Recommended fix Moderate confidence

Upgrade to a version newer than 2.5.4 (the latest available version from the WordPress plugin repository)

  1. 1. Log into the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Houzez Property Feed' plugin
  4. 4. Check the current installed version (should be 2.5.4 or lower based on the vulnerability description)
  5. 5. If an update is available, click 'Update Now' to upgrade to the latest version
  6. 6. Verify the update completed successfully and the plugin is now running a version newer than 2.5.4
  7. 7. Test the plugin functionality to confirm the update did not break any features

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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