dbcve.org
PHP File Inclusion (RFI/LFI)Weakness · CWE-98

CVE-2025-32656

HIGH · 8.1 CVSS v3.1 Published 2025-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in RadiusTheme Testimonial Slider And Showcase Pro testimonial-slider-showcase-pro allows PHP Local File Inclusion.This issue affects Testimonial Slider And Showcase Pro: from n/a through <= 2.3.15.

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

A Local File Inclusion (LFI) vulnerability exists in the RadiusTheme Testimonial Slider And Showcase Pro WordPress plugin. The vulnerability allows attackers to manipulate file path parameters used in PHP include/require statements, potentially enabling unauthorized reading of sensitive server files. This stems from insufficient input validation on file inclusion functions.

MitigationUpdate the plugin to the latest available version that addresses this vulnerability. If no patched version exists, consider disabling the plugin or implementing web application firewall (WAF) rules to block directory traversal patterns in the interim.

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
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 checks

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

  1. Verify the plugin is installed
    Check for the presence of the RadiusTheme Testimonial Slider And Showcase Pro plugin in your WordPress installation. Common paths include /wp-content/plugins/rt-testimonial-slider/ or similar. Use file system inspection or WordPress admin panel to confirm the plugin is active.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed version
    Access the WordPress admin panel under Plugins > Installed Plugins and locate the RadiusTheme Testimonial Slider And Showcase Pro entry. Alternatively, check the plugin's main PHP file for a version comment or header, typically found in the main plugin file in the plugin directory.
    Affected if The installed version matches or falls within the affected version range for this vulnerability.
  3. Check for exposed file inclusion parameters
    Examine your web server logs and application access logs for requests containing path traversal patterns such as ../, ..\, or absolute file paths in parameters that may be processed by the plugin's include/require functions. Common suspicious patterns include parameters like 'file', 'path', 'template', or 'page' with directory traversal sequences.
    Affected if Log analysis reveals requests with directory traversal patterns targeting the plugin's file inclusion functionality.
  4. Inspect for unauthorized file access
    Review server access logs for successful or attempted LFI attacks. Look for requests accessing system files like /etc/passwd, /etc/hosts, Windows system files, or other sensitive configuration files through the plugin's endpoints.
    Affected if Logs or file system inspection shows evidence of unauthorized access to server files through the plugin.
  5. Verify input validation controls
    If you have access to the plugin source code, examine PHP files for include, require, include_once, or require_once statements that use unsanitized variables from user input (e.g., $_GET, $_POST, $_REQUEST) in file paths.
    Affected if The plugin code contains file inclusion functions using unsanitized user input without proper validation or whitelisting.

A user is affected if the RadiusTheme Testimonial Slider And Showcase Pro plugin is installed and the vulnerable file inclusion mechanism can be reached, or if evidence of exploitation appears in logs or file system.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest available version that addresses this vulnerability. If no patched version exists, consider disabling the plugin or implementing web application firewall (WAF) rules to block directory traversal patterns in the interim.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32656 — 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-32656 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