UnitravelWordPress extension · Ancorathemes
CVE-2025-58900
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 · uneditedImproper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes UniTravel unitravel allows PHP Local File Inclusion.This issue affects UniTravel: from n/a through <= 1.4.2.
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 · moderate confidenceLocal File Inclusion vulnerability in the UniTravel WordPress theme allows attackers to include arbitrary local PHP files due to improper control of filename parameters in include/require statements. This could lead to remote code execution if an attacker can upload files to accessible locations or read sensitive files.
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
UnitravelWordPress extension
<= 1.4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm UniTravel theme is installedCheck your WordPress installation for the UniTravel theme (Ancorathemes Unitravel) in wp-content/themes/ directory or via WordPress admin appearance themes sectionAffected if The UniTravel theme by Ancorathemes is present in the WordPress installation
-
Check installed theme versionView the style.css file in the theme directory and locate the Version: header, or check via WordPress admin theme detailsAffected if The version is 1.4.2 or lower
-
Identify vulnerable file inclusion codeSearch theme PHP files for include() or require() statements using dynamic variables or parameters without proper sanitization (e.g., include($_GET['file']), include($file)), particularly in files within include/ or similar directoriesAffected if Dynamic file inclusion using unsanitized user input is found in the theme code
-
Check PHP allow_url_include settingCreate a PHPinfo page or check php.ini for the allow_url_include directive valueAffected if allow_url_include is set to On (1) in PHP configuration
-
Verify web server file permissionsReview file permissions on the web root and ensure PHP files cannot be written to accessible directories by unauthorized usersAffected if Web server permissions allow write access to directories that PHP can execute from (e.g., uploads/, cache/, or theme directories)
You are affected if the UniTravel theme version is 1.4.2 or lower AND the vulnerable file inclusion code exists in your installation AND conditions exist that could allow exploitation (file upload capability or accessible sensitive files).
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to a patched version of UniTravel theme when available. Until then, disable allow_url_include in PHP configuration, implement strict input validation on file inclusion parameters, and ensure web server permissions prevent unauthorized file access.
Fix this in Unitravel
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58900 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58900 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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