dbcve.org
Server-Side Request Forgery (SSRF)Weakness · CWE-918

CVE-2025-9975

MEDIUM · 6.8 CVSS v3.1 Published 2025-10-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
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
The WP Scraper plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 5.8.1 via the wp_scraper_extract_content function. This makes it possible for authenticated attackers, with Administrator-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. On Cloud instances, this issue allows for metadata retrieving.

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 WP Scraper plugin for WordPress contains a Server-Side Request Forgery (SSRF) vulnerability in the wp_scraper_extract_content function. Authenticated attackers with Administrator-level access can cause the server to make arbitrary HTTP requests to internal services or cloud metadata endpoints, potentially exposing sensitive information from internal infrastructure.

MitigationUpdate the WP Scraper plugin to version 5.8.2 or later which contains the security patch. If the plugin is not actively needed, consider removing it entirely to reduce attack surface.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/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. Confirm WP Scraper plugin is installed
    Navigate to WordPress admin > Plugins and look for 'WP Scraper' in the list, or query the database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' LIKE '%wp-scraper%';
    Affected if The plugin appears in the active plugins list
  2. Check the installed plugin version
    In WordPress admin > Plugins > WP Scraper, look at the version number displayed beneath the plugin name, or inspect the plugin main file header: /wp-content/plugins/wp-scraper/wp-scraper.php and read the Version tag in the plugin comment block
    Affected if The version number is lower than 5.8.2 (e.g., 5.8.1, 5.8.0, etc.)
  3. Verify the plugin is active
    Check if the plugin is enabled in WordPress admin > Plugins > WP Scraper. An inactive plugin with no users cannot be exploited, but still represents exposure if credentials are later obtained
    Affected if The plugin status shows 'Active'
  4. Confirm Administrator-level accounts exist
    In WordPress admin > Users, verify if any user accounts have the Administrator role. The vulnerability requires Administrator-level access to exploit
    Affected if At least one user with Administrator role exists and has access to the WordPress admin dashboard
  5. Check if content extraction feature is accessible
    Locate the WP Scraper settings or content extraction interface in the plugin admin menu (typically under WP Scraper > Templates or a similar section). The vulnerability exists in the wp_scraper_extract_content function used for scraping external URLs
    Affected if The plugin's scraping/content extraction feature is available and functional in the admin interface

You are affected if the WP Scraper plugin is installed, active, and running at a version lower than 5.8.2, with at least one Administrator-level user account that can access the plugin's content extraction functionality.

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 WP Scraper plugin to version 5.8.2 or later which contains the security patch. If the plugin is not actively needed, consider removing it entirely to reduce attack surface.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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