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

CVE-2024-43261

CRITICAL · 9.6 CVSS v3.1 Published 2024-08-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Hamed Naderfar Compute Links allows PHP Remote File Inclusion.This issue affects Compute Links: from n/a through 1.2.1.

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

This is a PHP Remote File Inclusion (RFI) vulnerability in the Compute Links component. The application fails to properly validate filenames used in include/require statements, allowing attackers to inject arbitrary file paths (including remote URLs) that get executed by the PHP interpreter, leading to remote code execution.

MitigationFix input validation on all include/require statements to use strict allowlists, apply basename() to strip directory traversal, disable allow_url_include in php.ini, and upgrade to any patched version beyond 1.2.1.

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 Compute Links component
    Search the codebase for files or directories named 'compute', 'links', or similar patterns containing the Compute Links functionality
    Affected if The component is present in the application
  2. Identify the installed version
    Check the component's version metadata (e.g., version file, composer.json, README, or header comments) and compare it to the patched version boundary
    Affected if The version is at or below the unpatched release (1.2.1 or lower)
  3. Review include/require statements
    Search the Compute Links source files for dynamic include/require statements where user input or external parameters feed directly into file paths without validation
    Affected if Dynamic file includes are present and accept unsanitized input
  4. Check PHP allow_url_include setting
    Inspect php.ini or run 'php -i' to check if the allow_url_include directive is enabled (set to On)
    Affected if allow_url_include is On, enabling remote URL injection in includes

A user is affected if the Compute Links component version is at or below 1.2.1 and contains dynamic include/require statements that accept unsanitized input, especially with allow_url_include enabled.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Fix input validation on all include/require statements to use strict allowlists, apply basename() to strip directory traversal, disable allow_url_include in php.ini, and upgrade to any patched version beyond 1.2.1.

Recommended fix Moderate confidence
  1. 1. Assess whether this application (Compute Links by Hamed Naderfar) is still actively maintained. The vendor did not provide a fixed version.
  2. 2. If the application is not actively maintained, plan to decommission and replace it with an actively supported alternative.
  3. 3. If the application must remain in use temporarily, immediately restrict web server configuration to prevent inclusion of remote files: disable allow_url_fopen and allow_url_include in php.ini.
  4. 4. Implement .htaccess rules to block suspicious request patterns targeting the vulnerable include/require statements.
  5. 5. Consider deploying a Web Application Firewall (WAF) as an interim mitigation layer.
  6. 6. Monitor patchstack.com and the vendor's distribution channel for any future security updates.
Caveat No fixed version is available from the vendor; the recommended path is to replace this software with an actively maintained alternative

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43261 — 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-43261 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