Wp PipesWordPress extension · Thimpress
CVE-2025-48267
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ThimPress WP Pipes allows Path Traversal. This issue affects WP Pipes: 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 confidenceA path traversal vulnerability in the ThimPress WP Pipes WordPress plugin allows attackers to access files outside the intended restricted directory. The CVSS 9.1 score indicates this is likely exploitable without authentication and can expose sensitive system 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
Wp PipesWordPress extension
< 1.4.3CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Locate WP Pipes plugin in WordPressCheck your WordPress plugins directory for a wp-pires folder, or look for the plugin in the WordPress admin under PluginsAffected if The WP Pipes plugin directory exists in your WordPress installation
-
Identify installed plugin versionView the plugin header in the main plugin PHP file or check the version displayed in WordPress admin under Plugins > Installed PluginsAffected if The version displayed is lower than 1.4.3
-
Confirm plugin is activeCheck the Plugins page in WordPress admin to see if WP Pipes shows as activeAffected if WP Pipes is currently activated on your WordPress site
-
Inspect plugin file handling functionsReview PHP files in the plugin directory for file operations that use user-supplied input without sanitization (such as include, require, fopen, file_get_contents with path variables)Affected if The plugin contains file handling code that could accept path traversal patterns from unauthenticated requests
Your environment is affected if WP Pipes plugin is installed, active, and running a version lower than 1.4.3, which allows unauthenticated path traversal attacks to access files outside the intended directory.
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 · scoped1.4.3
Update WP Pipes to the latest patched version. If no patch is available, disable the plugin until a fix is released. Implement web application firewall rules to block path traversal patterns (../, ..\) as a temporary mitigation.
WP Pipes version 1.4.3
- Update the WP Pipes plugin to version 1.4.3 or later through the WordPress admin dashboard under Plugins > All Plugins > WP Pipes > Update Now
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Wp Pipes
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2025-48267 — 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-48267 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