CVE-2025-69133
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 · uneditedSubscriber Local File Inclusion in Tourmaster <= 5.4.5 versions.
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 confidenceA Local File Inclusion (LFI) vulnerability in Tourmaster plugin/theme versions 5.4.5 and below allows authenticated Subscriber-level users to read arbitrary files on the server by manipulating file path parameters. This low-privilege user capability combined with the ability to read sensitive system files elevates the severity.
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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Tourmaster installation and versionLocate the Tourmaster plugin/theme files and check the main version file or header for the installed version numberAffected if The installed version is 5.4.5 or lower
-
Verify WordPress user roles existCheck the WordPress user management panel or database for users with Subscriber-level roleAffected if At least one Subscriber-level user account exists in the system
-
Confirm file inclusion functionality is presentInspect the Tourmaster code for file inclusion functions (include, require, readfile, file_get_contents) that accept user-supplied path parametersAffected if File inclusion functions that accept path parameters are present and accessible to subscribers
-
Test access to sensitive filesIf you have a test Subscriber account, attempt to access sensitive files like /etc/passwd or wp-config.php through Tourmaster file parameters (this is a proof-of-concept and should be done in a dev environment)Affected if A low-privilege Subscriber user can successfully read arbitrary server files
You are affected if Tourmaster version is 5.4.5 or below AND Subscriber-level user accounts exist in WordPress AND the vulnerable file inclusion functionality is accessible to those users.
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.
dbcve · scopedUpgrade Tourmaster to a version newer than 5.4.5. If immediate patching is not feasible, implement strict input validation and path sanitization on file inclusion functions, and consider temporarily restricting Subscriber-level account capabilities until the patch is applied.
Tourmaster version 5.4.6 or latest available (any version above 5.4.5)
- 1. Log in to your WordPress admin dashboard
- 2. Navigate to Plugins > Installed Plugins
- 3. Locate the Tourmaster plugin
- 4. If an update is available, click 'Update Now' to install the latest version
- 5. If no update appears in WordPress, manually download the latest version from WordPress.org or the official themeforest/vendor source
- 6. Deactivate the current Tourmaster plugin
- 7. Upload and install the new version
- 8. Reactivate the plugin
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-69133 — 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-69133 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