dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-69131

HIGH · 7.5 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Unauthenticated Arbitrary File Download in WordPress & WooCommerce Scraper Plugin, Import Data from Any Site <= 1.0.7 versions.

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 WordPress 'Import Data from Any Site' plugin versions 1.0.7 and below contains an unauthenticated arbitrary file download vulnerability, allowing remote attackers to retrieve any readable file from the server filesystem without authentication.

MitigationUpdate the plugin to version 1.0.8 or later. If immediate patching is not possible, disable the plugin and monitor for indicators of compromise.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 plugin installation
    Check if the 'Import Data from Any Site' plugin is installed in the WordPress environment by reviewing the plugin directory (wp-content/plugins/) or the WordPress admin Plugins page.
    Affected if The plugin is present in the plugins directory or listed in the WordPress admin.
  2. Check installed plugin version
    Locate the main plugin file (typically import-data-from-any-site.php or similar) and inspect the plugin header for the Version field, or view the version listed in the WordPress admin Plugins page.
    Affected if The installed version is 1.0.7 or lower.
  3. Confirm plugin is active
    In WordPress admin, verify whether the plugin is currently activated. The vulnerability is exploitable without authentication when the plugin is active.
    Affected if The plugin shows as 'Active' in the WordPress admin plugins list.
  4. Review access logs for suspicious requests
    Examine web server access logs (Apache/nginx) for unusual download requests to the plugin's endpoint, particularly requests containing file path parameters (e.g., ?file=, ?download=, or similar).

The environment is affected if the 'Import Data from Any Site' plugin is installed, active, and running version 1.0.7 or below.

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 plugin to version 1.0.8 or later. If immediate patching is not possible, disable the plugin and monitor for indicators of compromise.

Recommended fix Moderate confidence

Latest version available in WordPress plugin repository (greater than 1.0.7)

  1. 1. Identify the plugin: WordPress & WooCommerce Scraper Plugin - Import Data from Any Site
  2. 2. Check current installed version in WordPress plugin dashboard
  3. 3. If version is 1.0.7 or lower, update to the latest available version from the WordPress plugin repository
  4. 4. Verify the update was successful by checking the new version number
  5. 5. Test that the plugin functionality still works as expected after the 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 / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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