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

CVE-2024-12272

HIGH · 8.8 CVSS v3.1 Published 2024-12-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The WP Travel Engine – Elementor Widgets | Create Travel Booking Website Using WordPress and Elementor plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.3.7 via several widgets. This makes it possible for authenticated attackers, with Contributor-level access and above, to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

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

The WP Travel Engine Elementor Widgets plugin for WordPress contains a Local File Inclusion vulnerability in multiple widgets. Authenticated attackers with Contributor-level access or higher can include and execute arbitrary files on the server by manipulating file paths in vulnerable widget parameters, enabling PHP code execution.

MitigationUpdate the plugin to version 1.3.8 or later. Until updated, restrict Contributor-level users and audit user permissions, as the vulnerability can be exploited by any authenticated user.

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

CVSS:3.1/AV:N/AC:L/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. Verify WP Travel Engine - Elementor Widgets plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Travel Engine - Elementor Widgets' in the list. Note the installed version displayed.
    Affected if The plugin is installed and the version shown is earlier than 1.3.8 (or if no version is displayed, the plugin is likely outdated)
  2. Confirm Elementor page builder is active
    Check if Elementor Website Builder plugin is installed and active in Plugins > Installed Plugins. This plugin provides the widget infrastructure that the vulnerable plugin extends.
    Affected if Elementor is active and the WP Travel Engine - Elementor Widgets plugin is running a version before 1.3.8
  3. Identify user roles with Contributor-level access or higher
    In WordPress admin, go to Users > All Users and review the Role column. Look for accounts assigned 'Contributor', 'Author', 'Editor', or 'Administrator' roles.
    Affected if There are any user accounts with Contributor-level access or higher while the vulnerable plugin version is installed
  4. Check for active use of WP Travel Engine widgets
    Review pages/posts created with Elementor. Look for widgets from the 'WP Travel Engine' category in the Elementor editor panel (search for widgets like Trip Search, Trip Data, Pricing, etc.)
    Affected if Any WP Travel Engine Elementor widgets are in use on the site with a plugin version before 1.3.8

The environment is affected if WP Travel Engine - Elementor Widgets plugin version below 1.3.8 is installed, Elementor is active, and any users with Contributor-level or higher access exist on the site.

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 plugin to version 1.3.8 or later. Until updated, restrict Contributor-level users and audit user permissions, as the vulnerability can be exploited by any authenticated user.

Recommended fix Moderate confidence

Version 1.3.8 or later (check WordPress plugin repository for latest stable release)

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'WP Travel Engine – Elementor Widgets' plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, navigate to Dashboard > Updates and select the plugin to update
  6. After updating, verify the plugin is running version 1.3.8 or higher by checking the plugins list
  7. Review the site for any signs of compromise since the vulnerability was exploitable by authenticated users

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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