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

CVE-2025-7843

MEDIUM · 6.4 CVSS v3.1 Published 2025-09-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/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 Auto Save Remote Images (Drafts) plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0.9 via the fetch_images() function. This makes it possible for authenticated attackers, with Contributor-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.

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 Auto Save Remote Images (Drafts) WordPress plugin has a Server-Side Request Forgery (SSRF) vulnerability in the fetch_images() function. Authenticated users with Contributor-level access or higher can manipulate the plugin to make arbitrary web requests from the server, potentially accessing internal services or exfiltrating data.

MitigationUpdate the plugin to the latest available version. If no update is available, restrict or disable Contributor-level user accounts until a patch is released, as this privilege level can trigger the vulnerable fetch_images() function.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/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 the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Auto Save Remote Images (Drafts)' or search for it
    Affected if the plugin is installed and active
  2. Check the installed plugin version
    Click on the plugin in the Plugins list to view its details; compare the version number against any known affected version range
    Affected if the installed version falls within an affected version range and no patch has been applied
  3. Confirm the plugin is active
    In Plugins > Installed Plugins, verify the plugin status shows as 'Active'
    Affected if the plugin is active and a Contributor-level user can access it
  4. Identify Contributor-level user accounts
    In WordPress admin, go to Users and review the role assigned to each account; note any accounts with the Contributor role
    Affected if any Contributor-level accounts exist and can access the vulnerable fetch_images() function
  5. Test if fetch_images() is accessible
    As a Contributor user, attempt to access the plugin functionality that triggers fetch_images() - typically through a post draft or image save action
    Affected if the function can be triggered by Contributor-level users without admin oversight

You are affected if the Auto Save Remote Images (Drafts) plugin is active, runs a vulnerable version, and Contributor-level user accounts exist in your WordPress installation.

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 the latest available version. If no update is available, restrict or disable Contributor-level user accounts until a patch is released, as this privilege level can trigger the vulnerable fetch_images() function.

Recommended fix Moderate confidence

1.1.0 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the 'Auto Save Remote Images (Drafts)' plugin
  4. Click 'Update now' if an update is available, or manually update to version 1.1.0 or later
  5. Verify the plugin is updated by checking the version number in the plugins list

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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