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

CVE-2024-12811

HIGH · 8.8 CVSS v3.1 Published 2025-02-28
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 Traveler theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.1.9 via shortcodes. This makes it possible for authenticated attackers, with contributor-level and above permissions, 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 php file type 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 Traveler theme for WordPress contains a Local File Inclusion vulnerability in its shortcode handler, affecting all versions up to 3.1.9. Authenticated attackers with contributor-level permissions or higher can craft shortcode parameters to traverse directories and include arbitrary files, enabling PHP code execution.

MitigationUpdate the Traveler theme to version 3.2.0 or later. If immediate update is not possible, restrict contributor-level permissions and disable vulnerable shortcodes until the patch can be applied.

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. Identify the installed Traveler theme version
    Navigate to WordPress admin dashboard, go to Appearance > Themes, and locate the Traveler theme to view its current version number
    Affected if The displayed version is 3.1.9 or any earlier version (e.g., 3.1.8, 3.1.7, etc.)
  2. Confirm shortcode functionality is active
    Check if the WordPress shortcode API is enabled and the theme is registering shortcodes; this can be verified by reviewing the theme's functions.php for add_shortcode calls or by using a plugin to list active shortcodes
    Affected if Shortcodes are registered and functional within the theme
  3. Review user role permissions
    In WordPress admin, go to Users > All Users and examine the roles assigned; specifically identify accounts with Contributor-level or higher permissions (Contributor, Author, Editor, Administrator)
    Affected if There are one or more users with Contributor, Author, Editor, or Administrator roles who can access the WordPress admin area
  4. Inspect the shortcode handler for directory traversal vulnerability
    Examine the theme's shortcode handler code (typically in the theme's inc/ or includes/ directory) for parameters that include or require files without proper sanitization; look for shortcode functions that accept file paths in attributes and use include/require statements
    Affected if The shortcode handler accepts user-supplied path parameters and includes files without validating the path (e.g., no check for '../' sequences or whitelist validation)

A user is affected if the Traveler theme version is 3.1.9 or earlier AND shortcodes are enabled AND users with Contributor-level or higher permissions exist on the site, allowing potential LFI exploitation through the vulnerable shortcode handler.

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 Traveler theme to version 3.2.0 or later. If immediate update is not possible, restrict contributor-level permissions and disable vulnerable shortcodes until the patch can be applied.

Recommended fix Moderate confidence

Traveler theme version 3.2.0 or later (latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Appearance > Themes
  3. 3. Locate the Traveler theme in the themes list
  4. 4. Check the current version number of the installed Traveler theme
  5. 5. Download the latest version of the Traveler theme from the official source (travelerwp.com) or from a trusted WordPress theme marketplace
  6. 6. If available, ensure the new version is 3.2.0 or higher, as versions up to and including 3.1.9 are vulnerable
  7. 7. Update the Traveler theme to the latest version
  8. 8. Verify the update was successful by checking the theme version in the WordPress admin
Caveat Review theme customizations and child theme compatibility after upgrade, as template changes in new versions may affect custom styling or functionality

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