dbcve.org
Wp PipesWordPress extension · Thimpress

CVE-2025-28977

MEDIUM · 6.1 CVSS v3.1 Published 2025-08-20
Fix available
A fix is available. Upgrade to after 1.4.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in ThimPress WP Pipes allows Reflected XSS. 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 · moderate confidence

Reflected XSS vulnerability in ThimPress WP Pipes plugin allows attackers to inject malicious JavaScript through unsanitized user input that is reflected in web pages without proper output encoding. The vulnerability affects versions up to 1.4.3.

MitigationUpdate WP Pipes to the latest patched version once available. As a temporary measure, implement a WAF rule to filter XSS attack patterns in query parameters, and ensure all output is properly escaped using WordPress sanitization functions.

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
Affected:<= 1.4.3

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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Pipes plugin version
    In WordPress admin, go to Plugins > Installed Plugins and locate WP Pipes. The version number is displayed below the plugin name. Alternatively, check the plugin's main PHP file (typically in /wp-content/plugins/wp-pipes/ or /wp-content/plugins/wp-pipes/includes/) for the 'Version' header in the plugin comment block.
    Affected if The installed version is 1.4.3 or lower, or if no version number is displayed (indicating an unversioned pre-release install older than 1.4.3).
  2. Confirm WP Pipes plugin is active
    In WordPress admin, go to Plugins > Installed Plugins and verify that WP Pipes shows as 'Active'. You can also check the wp_options table in the database for the option 'active_plugins' and see if wp-pipes.php is listed.
    Affected if The plugin is active and the version is 1.4.3 or lower.
  3. Identify reflected input points
    Review plugin source code for pages that use superglobal inputs ($_GET, $_POST, $_REQUEST) directly in HTML output without escaping. Search for functions like echo, print, or printf that output request parameters. Common vulnerable patterns include PHP code that echoes query parameters back to the page, such as 'echo $_GET["param"];' or 'echo $_REQUEST["id"];' without sanitization functions like esc_html(), esc_attr(), or wp_kses().
    Affected if The plugin code contains direct reflection of user input without WordPress sanitization functions, and the version is 1.4.3 or lower.
  4. Check for vulnerable query parameter usage
    Examine the plugin's frontend-facing PHP files (in the main plugin directory or templates folder) for code that reads URL parameters and outputs them in page content. Look for patterns like '$_GET["pipe"]', '$_GET["id"]', or similar parameter usage echoed to HTML without esc_html() or esc_attr() wrapping.
    Affected if The plugin processes and reflects query string parameters directly into HTML output without encoding, on versions 1.4.3 or below.

A user is affected if the WP Pipes plugin is installed, active, and the installed version is 1.4.3 or lower, with unsanitized user input being reflected in web pages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.4.3
Interim mitigation

Update WP Pipes to the latest patched version once available. As a temporary measure, implement a WAF rule to filter XSS attack patterns in query parameters, and ensure all output is properly escaped using WordPress sanitization functions.

Fix this in Wp Pipes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-28977 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-28977 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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