dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2024-54263

HIGH · 7.5 CVSS v3.1 Published 2026-02-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Talemy Spirit Framework allows PHP Local File Inclusion.This issue affects Spirit Framework: from n/a through 1.2.13.

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 confidence

A PHP Local File Inclusion (LFI) vulnerability in the Talemy Spirit Framework allows attackers to include arbitrary local files due to improper control of filename parameters in include/require statements. This affects all versions through 1.2.13, enabling attackers to read sensitive files on the server.

MitigationUpdate to a patched version of the Spirit Framework if available. Otherwise, implement strict input validation and sanitization on file path parameters before use in include/require statements, and disable allow_url_fopen and allow_url_include in PHP configuration.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Talemy Spirit Framework installation
    Search your web server directories for the 'spirit' or 'talemy' folder, or check your project's composer.json for 'talemy/spirit-framework' dependency. Common paths include /wp-content/themes/ or /wp-content/plugins/ if bundled with WordPress.
    Affected if The framework is not found in your environment, you are not affected by this CVE.
  2. Determine the installed version of Spirit Framework
    Check the version.php, composer.json, or readme.txt file within the Spirit Framework directory. Look for a 'Version:' field or 'version' variable set to a numeric value.
    Affected if The installed version is 1.2.13 or any version through 1.2.13, meaning versions <= 1.2.13 are affected.
  3. Identify PHP files using include or require statements
    Search the Spirit Framework PHP files for patterns like 'include(', 'require(', 'include_once(', or 'require_once(' where a variable is passed as the file path, for example: 'include($file)', 'require($path)', 'include($_GET[...])', etc.
    Affected if Dynamic file inclusion using variables without sanitization is present in the codebase.
  4. Verify if user input reaches the file inclusion functions
    Trace the variables used in include/require statements backward through the code to determine if they originate from $_GET, $_POST, $_COOKIE, or other user-controllable sources without proper validation.
    Affected if User-supplied input (via GET, POST, cookies, or other HTTP parameters) flows directly to include/require statements without sanitization.
  5. Confirm the application exposes vulnerable parameters
    Test the application by submitting arbitrary paths through suspected parameters (such as ?file=, ?path=, ?page=) to see if the application attempts to include them. Review the application's routing or parameter handling to identify which inputs map to the vulnerable include calls.
    Affected if The application accepts file path parameters in HTTP requests that are processed by the vulnerable include/require code.

You are affected if the Talemy Spirit Framework version is 1.2.13 or below AND your installation contains dynamic file inclusion code where user-controlled parameters are passed directly to include/require statements without validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version of the Spirit Framework if available. Otherwise, implement strict input validation and sanitization on file path parameters before use in include/require statements, and disable allow_url_fopen and allow_url_include in PHP configuration.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-54263 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-54263 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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