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

CVE-2025-60126

HIGH · 8.8 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 PluginOps Testimonial Slider testimonial-add allows PHP Local File Inclusion.This issue affects Testimonial Slider: from n/a through <= 3.5.8.6.

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 confidence

A PHP Local File Inclusion vulnerability exists in the PluginOps Testimonial Slider plugin's testimonial-add functionality. The vulnerability allows attackers to include arbitrary PHP files from the server filesystem due to improper control of filename parameters in include/require statements, potentially leading to remote code execution.

MitigationUpdate the Testimonial Slider plugin to the latest patched version. If no patch is available, disable the plugin or implement web application firewall rules to block directory traversal patterns in the affected testimonial-add endpoint.

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

CVSS:3.1/AV:N/AC:L/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 checks

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

  1. Identify the PluginOps Testimonial Slider version
    Check the plugin header in the main plugin file (usually in wp-content/plugins/testimonial-slider/plugin.php or similar) or view the installed version in WordPress admin under Plugins
    Affected if The installed version is 3.5.8.6 or lower (any version up to and including 3.5.8.6 is affected)
  2. Confirm the testimonial-add component is active
    Verify the plugin is enabled and the testimonial-add functionality is accessible on the site. Check for any WordPress shortcodes or admin menu items related to adding testimonials
    Affected if The plugin is active and the testimonial-add component is accessible to users (the vulnerability exists in this component regardless of user role)
  3. Locate the vulnerable include/require logic
    Inspect the PHP files in the plugin directory, specifically looking for include() or require() statements in files handling the testimonial-add functionality. Search for dynamic file inclusion patterns that use user-supplied input
    Affected if The code uses unsanitized variables in include/require statements within the testimonial-add component (this is the vulnerable condition)
  4. Check web server file permissions
    Review file permissions on the plugin directory and critical system directories (such as /tmp, /var/tmp, any directories writable by the web server)
    Affected if The web server process has read access to sensitive local PHP files that could be included via the LFI vulnerability

You are affected if the PluginOps Testimonial Slider plugin version is 3.5.8.6 or lower and the testimonial-add component is accessible on your site.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Testimonial Slider plugin to the latest patched version. If no patch is available, disable the plugin or implement web application firewall rules to block directory traversal patterns in the affected testimonial-add endpoint.

Recommended fix Moderate confidence

Latest version of PluginOps Testimonial Slider (version > 3.5.8.6)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'PluginOps Testimonial Slider' plugin
  4. 4. Check the current installed version (should be <= 3.5.8.6)
  5. 5. If an update is available, click 'Update Now' to install the latest version
  6. 6. After updating, verify the plugin is functioning correctly on the site
  7. 7. If no update is available in the WordPress repository, contact PluginOps directly for the patched version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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