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

CVE-2025-60189

HIGH · 7.5 CVSS v3.1 Published 2025-11-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in PoloPag PoloPag – Pix Automático para Woocommerce wc-polo-payments allows PHP Local File Inclusion.This issue affects PoloPag – Pix Automático para Woocommerce: from n/a through <= 2.0.9.

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

This is a PHP Local File Inclusion (LFI) vulnerability in the PoloPag WooCommerce plugin (wc-polo-payments). The vulnerability allows attackers to include and execute arbitrary local PHP files on the server due to improper control of filename parameters in include/require statements. Successful exploitation could lead to sensitive data exposure or remote code execution.

MitigationUpdate PoloPag – Pix Automático para Woocommerce to the latest patched version as soon as available. If no patch exists, disable the plugin until a fix is released. Implement strict input validation and use whitelist approaches for any file inclusion logic.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Locate the PoloPag plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for a folder named 'wc-polo-payments', 'polopag', or similar variants. In WordPress admin, navigate to Plugins > Installed Plugins and look for 'PoloPag - Pix Automático para Woocommerce'.
    Affected if The PoloPag plugin is installed and active in WordPress.
  2. Identify the installed PoloPag version
    If the plugin is installed, access the plugin file directly via FTP or file manager. Common version file locations: wp-content/plugins/wc-polo-payments/wc-polo-payments.php or readme.txt. Open the main plugin PHP file and locate the 'Version' header comment or the version constant.
    Affected if The installed version is unpatched and falls within any vulnerable version range (if known). If version cannot be determined, treat as potentially vulnerable.
  3. Verify the plugin is active on the site
    In WordPress admin dashboard, go to Plugins > Installed Plugins and confirm whether PoloPag shows as 'Active'. Alternatively, check the wp_options table for active_plugins entry.
    Affected if The plugin is currently activated on the WordPress site.
  4. Inspect for vulnerable file inclusion code patterns
    Access the plugin files via FTP or file manager. Search for include, require, include_once, or require_once statements that use variables in the path (e.g., include($file), require($_GET['page']), include($_POST['file'])). Check files in the plugin directory for dynamic file inclusion without sanitization.
    Affected if The plugin contains include/require statements using unsanitized user-controlled input (like $_GET, $_POST, or未经处理的变量) to load local files.
  5. Check server configuration for LFI exposure
    Review the web server configuration (Apache .htaccess, Nginx config) and PHP configuration (php.ini: allow_url_include, open_basedir). Check if the server has restrictive permissions preventing inclusion of sensitive files outside the web root.
    Affected if The server allows inclusion of arbitrary files and does not have restrictions on file path traversal or base directory constraints.

A user is affected if the PoloPag plugin is installed and active with a vulnerable version that contains unsafe file inclusion code, and the server configuration permits path traversal or arbitrary file access.

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 PoloPag – Pix Automático para Woocommerce to the latest patched version as soon as available. If no patch exists, disable the plugin until a fix is released. Implement strict input validation and use whitelist approaches for any file inclusion logic.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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