Wp PipesWordPress extension · Thimpress
CVE-2025-28979
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 ThimPress WP Pipes allows PHP Local File Inclusion. This issue affects WP Pipes: from n/a through 1.4.3.
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 confidenceA PHP Local File Inclusion (LFI) vulnerability in the ThimPress WP Pipes plugin (versions through 1.4.3) allows attackers to control filenames used in include/require statements, potentially enabling arbitrary PHP code execution by including malicious local 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Verify WP Pipes plugin is installedNavigate to WordPress admin dashboard > Plugins. Look for 'WP Pipes' or 'Thimpress WP Pipes' in the installed plugins list.Affected if The plugin appears in the installed plugins list and is activated.
-
Check installed WP Pipes versionIn WordPress admin > Plugins, locate WP Pipes and view the version number displayed beneath the plugin name. Alternatively, check the plugin header in wp-content/plugins/wp-pipes/plugin.php for the 'Version' comment tag.Affected if The displayed version is 1.4.3 or any version lower (e.g., 1.4.2, 1.4.1, 1.0.0).
-
Identify vulnerable include/require code patternsExamine the plugin PHP files for include/require statements that use unsanitized variables from request parameters. Look for patterns like 'include($_GET[...])' or 'require($var)' within the wp-pipes directory.Affected if The plugin code contains include/require statements using raw $_GET, $_POST, or $_REQUEST variables without sanitization.
-
Check for directory traversal in server access logsReview Apache/Nginx access logs (typically in /var/log/apache2/access.log or /var/log/nginx/access.log) for requests to the WP Pipes plugin that contain '../' patterns or absolute file paths in query parameters.Affected if Logs show requests to wp-pipes PHP files with path traversal sequences (e.g., '?file=../../../etc/passwd') or attempts to include sensitive server files.
A user is affected if the WP Pipes plugin is installed with version 1.4.3 or lower, and the vulnerable include/require code patterns are present in the plugin 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 WP Pipes to the latest patched version; if no update is available, disable the plugin until a fix is released, and review code for insecure file inclusion patterns.
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-28979 — 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-28979 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