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

CVE-2025-47571

HIGH · 7.5 CVSS v3.1 Published 2025-09-09
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 highwarden Super Store Finder superstorefinder-wp allows PHP Local File Inclusion.This issue affects Super Store Finder: from n/a through < 7.8.

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

The Super Store Finder WordPress plugin (superstorefinder-wp) versions before 7.8 contains a Local File Inclusion (LFI) vulnerability where the application does not properly sanitize input used in PHP include/require statements, allowing attackers to include arbitrary local PHP files via manipulated file paths.

MitigationUpgrade Super Store Finder plugin to version 7.8 or later to obtain the vendor patch. As a temporary measure, ensure PHP's allow_url_include is disabled and consider implementing WAF rules to block directory traversal patterns in HTTP requests.

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. Check Super Store Finder plugin version
    Log into WordPress admin, navigate to Plugins > Installed Plugins, locate 'Super Store Finder' and read the version number from the plugin description; alternatively, open the main plugin file (typically /wp-content/plugins/superstorefinder-wp/super-store-finder.php) and look for the 'Version:' header in the file comments
    Affected if Installed version is lower than 7.8 (e.g., 7.7, 7.6, etc.)
  2. Identify PHP files handling include/require with external input
    Search the plugin directory (/wp-content/plugins/superstorefinder-wp/) for PHP files containing include, include_once, require, or require_once statements that use variables from $_GET, $_POST, or $_REQUEST without proper sanitization; grep patterns like 'include($_' or 'require($_REQUEST'
    Affected if Files exist that perform dynamic file inclusions using unsanitized user-supplied parameters
  3. Verify the plugin's file inclusion endpoints are accessible
    Examine the plugin's PHP files to identify which scripts handle HTTP requests (check for code that processes $_GET['file'], $_GET['page'], or similar parameters passed to include/require functions); attempt a safe test request to confirm the endpoint responds
    Affected if HTTP-accessible endpoints exist that pass user parameters to include/require functions without validation
  4. Confirm PHP configuration allows file inclusion attacks
    Check php.ini for the allow_url_include setting (should be Off to mitigate, though this is for remote file inclusion - LFI works regardless); also verify that the web server user has read access to sensitive local files outside the web root
    Affected if PHP configuration permits the web process to read arbitrary local files that the web server user can access
  5. Inspect .htaccess or WAF rules for traversal protection
    Examine the site's .htaccess files and any WAF configuration for rules that block directory traversal patterns such as '../', '..\', or null byte injections in URL parameters; test by sending a request with '../' to see if it is blocked or filtered
    Affected if No traversal protection exists and requests with '../' are not blocked or sanitized by the web server or application layer

If the Super Store Finder plugin version is below 7.8 AND the plugin exposes file inclusion endpoints using unsanitized user input, the environment is likely affected by this LFI vulnerability.

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

Upgrade Super Store Finder plugin to version 7.8 or later to obtain the vendor patch. As a temporary measure, ensure PHP's allow_url_include is disabled and consider implementing WAF rules to block directory traversal patterns in HTTP requests.

Recommended fix Moderate confidence

7.8

  1. Backup your WordPress database and files before making any changes
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate 'Super Store Finder' in the plugin list
  4. Click 'Update now' if an update is available, or manually upload version 7.8 of the plugin
  5. Verify the plugin has been updated to version 7.8
  6. Clear any caching mechanisms (site cache, CDN cache)
  7. Test the Super Store Finder functionality to ensure the plugin works correctly after update
  8. Verify the vulnerability is no longer exploitable by confirming the fixed code is in place
Caveat Review plugin settings and customizations after upgrade as with any plugin update

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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