dbcve.org
TravelerWordPress extension · Shinecommerce

CVE-2025-1771

CRITICAL · 9.8 CVSS v3.1 Published 2025-03-15
Fix available
A fix is available. Upgrade to 3.1.9 or later.
See remediation →
100/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
The Traveler theme for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.1.8 via the 'hotel_alone_load_more_post' function 'style' parameter. This makes it possible for unauthenticated attackers 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 WordPress theme contains a Local File Inclusion (LFI) vulnerability in the 'hotel_alone_load_more_post' function via the 'style' parameter, allowing unauthenticated attackers to include arbitrary files and execute PHP code on the server. This critical flaw enables complete remote code execution by leveraging the lack of input sanitization on the style parameter.

MitigationImmediately update the Traveler theme to version 3.1.9 or later if available; otherwise, disable the affected function or implement input validation/sanitization on the 'style' parameter to restrict file inclusion to allowed paths only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TravelerWordPress extension
Affected:< 3.1.9

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Identify if Traveler theme is installed
    Check the wp-content/themes/ directory for a folder named 'traveler', 'traveler-hotel', or similar Traveler theme directories. Also check wp-admin/themes.php for the theme in the WordPress admin panel.
    Affected if The Traveler theme by Shinecommerce is present in the WordPress installation
  2. Determine the installed Traveler theme version
    Locate the style.css file within the Traveler theme folder and read the 'Version:' header in the file comments at the top, or check version information in the theme's functions.php
    Affected if The version number found is less than 3.1.9 (e.g., 3.1.8, 3.1.7, etc.)
  3. Locate the vulnerable hotel_alone_load_more_post function
    Search the Traveler theme folder for the string 'hotel_alone_load_more_post' using grep or a file search tool to identify if this function exists in the codebase.
    Affected if The function 'hotel_alone_load_more_post' is found in the theme files
  4. Verify the style parameter handling in the vulnerable function
    Examine the hotel_alone_load_more_post function code to confirm it accepts a 'style' parameter and uses it in a file inclusion mechanism (such as include, require, include_once, or require_once) without proper sanitization.
    Affected if The function uses the 'style' parameter in a file inclusion call without sanitizing the input

You are affected if the Traveler theme is installed with a version prior to 3.1.9 and the vulnerable hotel_alone_load_more_post function exists with an unsanitized 'style' parameter for file inclusion.

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
Upgrade available Upgrade to 3.1.9 or later
Fixed in 3.1.9
Interim mitigation

Immediately update the Traveler theme to version 3.1.9 or later if available; otherwise, disable the affected function or implement input validation/sanitization on the 'style' parameter to restrict file inclusion to allowed paths only.

Recommended fix High confidence

Traveler theme version 3.1.9

  1. Log in to WordPress admin dashboard
  2. Navigate to Appearance > Themes
  3. Locate the Traveler theme and update to version 3.1.9 or later
  4. Verify the update was applied successfully by checking the theme version

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

Fix this in Traveler Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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