CVE-2025-52808
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 real-web RealtyElite realtyelite allows PHP Local File Inclusion.This issue affects RealtyElite: from n/a through <= 1.0.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 confidenceA Local File Inclusion (LFI) vulnerability in the RealtyElite PHP application allows attackers to manipulate file path parameters used in include/require statements, potentially reading sensitive server files or achieving code execution through PHP wrapper techniques.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Locate RealtyElite installationSearch web server document roots for directories containing 'realtyelite', 'realty', or 'RealtyElite' folder names. Check common paths like /var/www/, /home/*/public_html/, or C:\inetpub\wwwroot\Affected if RealtyElite PHP application is present on the server
-
Identify installed versionLook for version files such as VERSION.txt, version.php, or a config file containing version information. Check the main index.php or README file for version stringsAffected if Installed version cannot be determined or falls within an affected version range
-
Find file inclusion code patternsSearch PHP source files for include, require, include_once, or require_once statements that use variables without proper sanitization. Use grep: grep -rn '\$.*include\|require' --include='*.php'Affected if User-supplied parameters (GET, POST, REQUEST) are used directly in include/require statements without validation
-
Identify vulnerable parametersExamine the file inclusion calls found and trace whether $_GET, $_POST, or $_REQUEST variables flow into the file path without whitelist validation or path sanitizationAffected if Parameters like 'page', 'file', 'template', 'path', or similar user-controllable values are used in include/require statements
-
Verify PHP wrapper exploitation potentialTest whether the application allows PHP wrapper protocols (php://filter, php://input) in the vulnerable parameter by submitting values like 'php://filter/convert.base64-encode/resource=config'Affected if The application accepts and processes PHP wrapper protocols in the vulnerable parameter
The environment is affected if RealtyElite PHP application is installed and contains file inclusion code that uses user-supplied input directly in include/require statements without validation or sanitization.
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 dataImplement strict input validation using whitelist approaches for any user-supplied data used in file inclusion operations, and refactor code to avoid direct use of user input in include/require statements.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52808 — 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-52808 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