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

CVE-2024-47323

HIGH · 8.1 CVSS v3.1 Published 2024-10-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 Ex-Themes WP Timeline – Vertical and Horizontal timeline plugin wp-timelines.This issue affects WP Timeline – Vertical and Horizontal timeline plugin: from n/a through <= 3.6.7.

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

This is a PHP Remote File Inclusion (RFI) vulnerability in the WP Timeline WordPress plugin. The flaw allows remote attackers to include arbitrary remote files via PHP's include/require statements due to improper control of filename parameters, likely from unsanitized user input. This can lead to remote code execution on the affected system.

MitigationUpdate the WP Timeline plugin to the latest version immediately. If no patched version is available, disable the plugin and consider deploying a WAF rule to block malicious file inclusion attempts as a temporary 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
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 checks

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

  1. Confirm WP Timeline plugin installation
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Timeline' or 'Timeline Express' in the plugin list. Alternatively, check the /wp-content/plugins/ directory for a folder containing 'timeline' in its name.
    Affected if The plugin is installed and active in WordPress
  2. Identify installed WP Timeline version
    In WordPress admin, go to Plugins > Installed Plugins and locate the WP Timeline plugin to view its version number. If not visible in admin, check the plugin's main PHP file header or the readme.txt file in the plugin directory.
    Affected if The installed version matches or falls within any affected version range (compare to vendor release notes for unpatched versions)
  3. Identify vulnerable file inclusion endpoint
    Inspect the plugin's PHP source files, particularly any handler or callback files that process include/require statements. Look for functions that accept user input (via $_GET, $_POST, or similar) and pass it directly to include, require, include_once, or require_once without sanitization.
    Affected if The plugin contains code that uses include/require with unsanitized user-supplied parameters (e.g., ?file=, ?page=, ?path=)
  4. Verify the vulnerable parameter is accessible
    Test the suspected endpoint by making a request with a remote URL as the parameter value (e.g., ?file=http://example.com/malicious). Check if the plugin attempts to fetch or include the external file.
    Affected if The vulnerable parameter is accessible and accepts remote URLs without validation

The environment is affected if the WP Timeline plugin is installed and contains the insecure file inclusion code that allows unsanitized user input to control include/require statements.

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

Update the WP Timeline plugin to the latest version immediately. If no patched version is available, disable the plugin and consider deploying a WAF rule to block malicious file inclusion attempts as a temporary measure.

Recommended fix Moderate confidence

Latest version beyond 3.6.7 from WordPress plugin repository

  1. Update the WP Timeline – Vertical and Horizontal timeline plugin to the latest available version from the WordPress plugin repository
  2. After updating, verify that the plugin functions correctly on the site
  3. Review any changes in plugin behavior or settings after the update
  4. Ensure WordPress core and other plugins are also kept up to date

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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