CVE-2025-32577
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 hakeemnala Build App Online build-app-online allows PHP Local File Inclusion.This issue affects Build App Online: from n/a through <= 1.0.23.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability in hakeemnala Build App Online (version <= 1.0.23) allows attackers to read sensitive local files on the server via improper validation of user-supplied input in PHP include/require statements. This critical flaw stems from directly incorporating unsanitized user input into file inclusion functions.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of Build App OnlineLocate the version file or header in the application installation directory, typically found in a version.php file, composer.json, or the admin dashboard under system information. Compare the version number to 1.0.23.Affected if The installed version is 1.0.23 or lower.
-
Locate PHP files using include or require with variable inputSearch the source code for patterns like 'include($_GET[', 'require($_POST[', 'include($', or similar constructs where user-supplied parameters are directly passed to file inclusion functions. Inspect the identified files for unsanitized input usage.Affected if Files exist that pass GET, POST, or other user-supplied parameters directly to include, include_once, require, or require_once functions without validation.
-
Identify the vulnerable parameter namesExamine the code found in the previous step to determine which specific query parameters (e.g., page, file, template, lang) are used in the file inclusion logic. Note these parameter names.Affected if User-controllable parameters are used in include/require statements without allowlist validation or sanitization.
-
Test for LFI by attempting benign file inclusionUsing a controlled request, attempt to include a known safe file (such as a configuration file or system file accessible in the web root) via the identified vulnerable parameter. For example: ?param=../../config.php or ?param=../../index.php. Observe whether the file contents are rendered or disclosed.Affected if The application returns the contents of files outside the intended directory, confirming the LFI vulnerability is exploitable.
You are affected if the installed version is 1.0.23 or lower AND the application contains PHP code that uses unsanitized user input in include/require statements, which can be exploited to read arbitrary local files.
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 dataRemediate by implementing strict allowlist-based validation for file inclusion parameters, avoiding direct use of user input in include/require statements, and upgrading to the latest version if a patched release is available.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32577 — 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-32577 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