CVE-2025-32150
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Rameez Iqbal Real Estate Manager real-estate-manager allows PHP Local File Inclusion.This issue affects Real Estate Manager: from n/a through <= 7.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 · high confidenceImproper control of filename for include/require statements in the Real Estate Manager PHP application allows attackers to manipulate file inclusion parameters, potentially enabling remote code execution or sensitive file disclosure through PHP Local/Remote File Inclusion.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Locate Real Estate Manager installationSearch the web root for files named 'realestate.php' or directories named 'real-estate-manager', 'realestate', or similar patterns. Common paths include /wp-content/plugins/real-estate-manager/ (WordPress) or /components/com_realestate/ (Joomla).Affected if The Real Estate Manager PHP application is present on the server.
-
Identify the installed versionCheck for a version file such as 'version.php', 'config.php', or a changelog/readme file within the Real Estate Manager directory. Look for a variable like $version or $rem_version.Affected if The installed version cannot be determined or is earlier than the patched release.
-
Check for vulnerable file inclusion parametersSearch PHP source files in the Real Estate Manager directory for include, require, include_once, or require_once statements that use variables in the file path, e.g., 'include($file)', 'require($_GET["page"])', or similar dynamic file inclusion patterns.Affected if Dynamic file inclusion using unsanitized user input is found in include/require statements.
-
Test for exposed file inclusion endpointsIdentify PHP files that handle page/task/action parameters (commonly index.php, router.php, or controller files). Attempt to manipulate these parameters with paths like '../../../../etc/passwd' or a remote URL to see if file contents are returned.Affected if The application returns file contents or executes included remote/local files based on user-controlled parameters.
-
Inspect PHP configuration for remote file inclusionCheck the php.ini configuration file (or run 'php -i' | grep 'allow_url_include') to determine if allow_url_include is enabled.Affected if allow_url_include is enabled, allowing remote file inclusion attacks.
A user is affected if the Real Estate Manager PHP application is installed with dynamic file inclusion using unsanitized input and the vulnerable parameters are accessible without authentication.
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 Real Estate Manager to a patched version. If no patch available, implement strict input validation with whitelist-based allowlisting for file inclusion paths and disable remote file inclusion in PHP configuration.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32150 — 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-2025-32150 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