CVE-2024-54270
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 Axeptio Axeptio axeptio-sdk-integration allows PHP Local File Inclusion.This issue affects Axeptio: from n/a through <= 2.5.4.
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 Axeptio SDK (versions up to 2.5.4) allows attackers to include arbitrary local PHP files due to improper control of filenames in include/require statements. This can lead to remote code execution if attacker-controlled files exist on the server or can be uploaded.
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.
-
Identify Axeptio SDK versionCheck your composer.json, composer.lock, or vendor directory for the installed axeptio-sdk version. Look for 'axeptio/sdk' or similar package names.Affected if The installed version is 2.5.4 or lower, or the version cannot be determined (treat as vulnerable).
-
Locate include/require statements in Axeptio SDKSearch the vendor/axeptio directory for dynamic file inclusions using variables or parameters, such as: include($file), require($path), include_once($_GET[...]), require_once($_POST[...]).Affected if The SDK code contains include/require statements that use dynamic variables without sanitization.
-
Verify user input reaches file inclusionTrace how parameters flow from HTTP requests (GET/POST) into the include/require calls found in step 2. Review controller and endpoint code that uses the Axeptio SDK.Affected if User-controllable input from HTTP requests can reach the vulnerable include/require paths without validation.
-
Check for writable directoriesIdentify directories on the server that are writable by the web server process, including upload directories, cache folders, and temp directories.Affected if Writable directories exist that could contain malicious PHP files for inclusion.
You are affected if you are running Axeptio SDK version 2.5.4 or lower AND your application passes user input to file inclusion functions in the SDK without validation.
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 whitelist-based validation for file paths used in include/require statements, ensuring only allowed files can be included. Remove or restrict any user-controllable input from file path parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-54270 — 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-54270 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