TripsterWordPress extension · Axiomthemes
CVE-2025-60048
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 axiomthemes Tripster tripster allows PHP Local File Inclusion.This issue affects Tripster: from n/a through <= 1.0.10.
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 Tripster WordPress theme allows attackers to manipulate filename parameters in include/require statements to read arbitrary local files. The lack of proper input validation on file inclusion paths enables attackers to access sensitive files such as wp-config.php, potentially exposing database credentials and other secrets.
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
TripsterWordPress extension
<= 1.0.10CVSS 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.
-
Identify if Tripster theme is installedCheck the theme directory for Tripster: look in wp-content/themes/ for a folder named 'tripster' or similar. In WordPress admin, go to Appearance > Themes to list installed themes.Affected if Tripster theme by Axiomthemes is present in the WordPress installation
-
Determine the installed version of Tripster themeOpen the theme's style.css file in wp-content/themes/tripster/ and look for the 'Version:' header in the CSS comments. Alternatively, check theme.json or functions.php for a version definition.Affected if The version number is 1.0.10 or lower
-
Locate file inclusion code in theme filesSearch theme PHP files (particularly in include/require statements) for dynamic file inclusion patterns using variables in the file path, such as: include($_GET['filename']) or require($file) or similar constructs where user input flows to file paths.Affected if The theme contains include/require statements that use unsanitized input parameters for file paths
-
Check for accessible vulnerable endpointsIf the theme exposes PHP files that handle file inclusion parameters (commonly in files named include.php, load.php, template.php, or similar), attempt to identify if these accept filename/path parameters via GET or POST requests.Affected if The theme has accessible PHP endpoints that accept filename parameters without proper validation
-
Verify wp-config.php accessibilityAttempt to access wp-config.php through the suspected vulnerable file inclusion parameter using path traversal (e.g., ../../wp-config.php) to confirm if arbitrary file read is possible.Affected if The file inclusion mechanism allows path traversal and successfully reads wp-config.php or other sensitive files
A user is affected if the Tripster theme version is 1.0.10 or lower and the theme contains accessible file inclusion code that accepts unsanitized filename parameters.
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 dataUpgrade to the latest version of Tripster theme which addresses the file inclusion vulnerability. If no patch is available, implement input validation using an allowlist approach for all include/require statements and disable allow_url_include in PHP configuration.
Fix this in Tripster
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-60048 — 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-60048 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