CVE-2024-44023
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 abcapp ABCApp Creator abcapp-creator.This issue affects ABCApp Creator: from n/a through <= 1.1.2.
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 Remote File Inclusion (RFI) vulnerability in ABCApp Creator allows attackers to control filenames used in PHP include/require statements, potentially enabling remote code execution by including malicious external files.
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.
-
Confirm ABCApp Creator installation and versionSearch the system for ABCApp Creator files (e.g., look for directories named 'abcapp', 'abcappcreator', or check web server document roots for the application). Check version.php, config files, or the application's main index page for a version string.Affected if ABCApp Creator is installed and the version cannot be confirmed as patched, or no version information is available to verify.
-
Locate PHP files handling include/require statementsSearch the application's PHP source code for dynamic include, include_once, require, or require_once statements. Use grep or similar: grep -r 'include\|require' --include='*.php' /path/to/abcapp.Affected if The application contains PHP files using include/require with variable or user-controlled paths.
-
Inspect parameters controlling file inclusion pathsExamine the include/require statements found and trace whether any URL parameters, POST data, or cookies feed into the file path. Look for patterns like include($_GET['file']) or require($var).Affected if User-supplied input (GET, POST, cookies, or HTTP headers) flows directly into include/require statements without sanitization.
-
Verify allowlist or validation on file inclusion parametersReview the code around dynamic includes to determine if input validation exists. Check for functions that validate the included file against an allowlist, or that strip ../ sequences, or that verify the file exists locally.Affected if No input validation, allowlist, or path sanitization exists on the parameters controlling file inclusion.
-
Test if external URLs can be includedIf the application accepts full URLs in file inclusion parameters, attempt a test include of a benign local file first (e.g., include('/etc/passwd') or include('http://example.com')) to confirm the vulnerability is exploitable.Affected if The application accepts absolute paths, absolute URLs, or paths with protocol wrappers (http://, php://) in include/require parameters.
A user is affected if ABCApp Creator is installed and its PHP code contains include/require statements that accept user-controlled input without validation, allowing external files to be included.
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 allowlists for file inclusion paths, replace dynamic file includes with static includes where possible, and upgrade to the latest patched version if available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-44023 — 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-44023 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