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

CVE-2024-38735

HIGH · 7.5 CVSS v3.1 Published 2024-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 Bastien Ho Event post event-post.This issue affects Event post: from n/a through <= 5.9.5.

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 · high confidence

A Remote File Inclusion (RFI) vulnerability in the Bastien Ho Event post plugin for WordPress allows attackers to include arbitrary remote files via unsanitized user input in PHP include/require statements. This can lead to remote code execution if attackers can upload or reference malicious PHP files.

MitigationImplement strict input validation and sanitization on all parameters used in include/require statements, preferably using an allowlist approach. Consider disabling allow_url_include in PHP configuration as a defense-in-depth measure.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Identify if the Bastien Ho Event post plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Bastien Ho Event post' or 'event-post' plugin. Alternatively, check the /wp-content/plugins/ directory for a folder named 'event-post' or similar.
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed plugin version
    In WordPress admin, click on the plugin name in the Plugins list to view its details, which typically displays the version number. Alternatively, open the main plugin PHP file (usually event-post.php or similar in the plugin folder) and look for the 'Version' header in the plugin comments.
    Affected if The version is unknown or falls within any vulnerable version range (no specific safe version was identified in the CVE data)
  3. Identify if the vulnerable parameter is accessible
    Examine the plugin source code files (particularly those handling form submissions or URL parameters) for include/require statements that use $_GET, $_POST, or $_REQUEST variables without sanitization. Look for patterns like 'include($_REQUEST["page"])' or similar user-input-driven include statements.
    Affected if The plugin code contains include/require statements using unsanitized user input from URL parameters
  4. Check PHP allow_url_include setting
    Create a PHP file with '<?php echo ini_get("allow_url_include"); ?>' and access it via a web browser, or check php.ini directly for the 'allow_url_include' directive.
    Affected if allow_url_include is enabled (set to On), which allows PHP to include remote URLs
  5. Verify if the plugin is exposed to unauthenticated users
    Test accessing plugin functionality without authentication. Try submitting requests to plugin endpoints using tools like Burp Suite or curl to see if the vulnerable parameter can be manipulated without logging in.
    Affected if The vulnerable parameter can be accessed and manipulated by unauthenticated users

Your environment is affected if the Bastien Ho Event post plugin is installed and the vulnerable code path with unsanitized user input in include/require statements is accessible, especially with allow_url_include enabled in PHP.

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

Implement strict input validation and sanitization on all parameters used in include/require statements, preferably using an allowlist approach. Consider disabling allow_url_include in PHP configuration as a defense-in-depth measure.

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-38735 — 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-38735 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