Build App OnlineWordPress extension · Buildapp
CVE-2024-49649
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 · moderate confidenceA PHP Local File Inclusion (LFI) vulnerability in the Build App Online application (versions up to 1.0.23) allows attackers to include arbitrary local PHP files via unsanitized input to include/require statements. This can lead to sensitive file disclosure, code execution, and potentially remote code execution if the attacker can upload files to accessible locations.
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
Build App OnlineWordPress extension
<= 1.0.23CVSS 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 Build App Online installationLocate the application web root directory. Search for typical Build App Online file structures such as index.php, configuration files, or the buildapp directory. Check web server document roots for the application.Affected if The application is found running on the server.
-
Determine installed versionLocate and read the version file or configuration. Check for version.php, VERSION files, or the main index.php that may display the version number. Compare against the affected range of <= 1.0.23.Affected if The installed version is 1.0.23 or lower.
-
Identify include/require usage with user inputSearch the application source code for include, require, include_once, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without sanitization. Look for patterns like 'include($_GET["page"])' or similar dynamic includes.Affected if Dynamic file inclusion using unsanitized user input is found in the codebase.
-
Check exposed parametersReview application routes and parameters that accept file or page names. Test if the application accepts and processes file paths through URL parameters (e.g., ?page=filename, ?file=path).Affected if The application accepts unvalidated file path parameters in HTTP requests.
-
Verify web server configurationReview the web server (Apache/Nginx) configuration for the application. Check if the application root has proper access restrictions and if PHP execution is restricted in upload directories.Affected if Web server allows direct access to included files or permits PHP execution in writable directories.
A user is affected if Build App Online version 1.0.23 or lower is running and the application contains dynamic include/require statements that process unsanitized user-supplied file paths.
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 with allowlisting for file paths, avoid using user input directly in include/require statements, and consider migrating to a modern framework that handles file operations more securely.
Fix this in Build App Online
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49649 — 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-2024-49649 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