dbcve.org
Url Media UploaderWordPress extension · Apprhyme

CVE-2025-1662

MEDIUM · 6.4 CVSS v3.1 Published 2025-02-28
Fix available
A fix is available. Upgrade to after 1.0.1 or later.
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 URL Media Uploader plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.0.0 via the 'url_media_uploader_url_upload' action. This makes it possible for authenticated attackers, with author-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 URL Media Uploader WordPress plugin has an SSRF vulnerability in the 'url_media_uploader_url_upload' action through version 1.0.0. Authenticated users with author-level permissions or higher can cause the server to make arbitrary HTTP requests to internal or external resources, potentially exposing internal services and data.

MitigationUpdate the plugin to the latest version if available, or remove/disable the plugin until a patch is released. Restrict user permissions to below author-level as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Url Media UploaderWordPress extension
Affected:<= 1.0.1

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. Identify if the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Apprhyme Url Media Uploader' or 'Url Media Uploader', or check the /wp-content/plugins/ directory for folders containing 'url-media-uploader' or similar naming
    Affected if The plugin is present in the WordPress installation
  2. Determine the installed version
    In WordPress admin, go to Plugins > Installed Plugins, find the plugin, and check the version number displayed beneath the plugin name. Alternatively, read the main plugin PHP file and look for a 'Version' header comment
    Affected if The version is 1.0.1 or lower, or if no version is displayed and the plugin is present (version unknown)
  3. Check if the vulnerable action exists
    Examine the plugin files for the 'url_media_uploader_url_upload' action hook. This is typically found in the main plugin PHP file or an admin/ajax handler file. Search for 'add_action' calls containing 'url_media_uploader_url_upload'
    Affected if The action hook 'url_media_uploader_url_upload' is registered and present in the code
  4. Verify if author-level or higher users exist
    In WordPress admin, go to Users > All Users and review the roles assigned. Check if any users have 'Author', 'Editor', 'Administrator', or other roles at level 7 or higher
    Affected if There are users with Author, Editor, or Administrator roles (or any role with publish_posts capability)

You are affected if the Apprhyme Url Media Uploader plugin (version 1.0.1 or lower) is installed AND the url_media_uploader_url_upload action exists AND there are users with author-level permissions or higher on the site.

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
Upgrade available Upgrade to a release after 1.0.1
Interim mitigation

Update the plugin to the latest version if available, or remove/disable the plugin until a patch is released. Restrict user permissions to below author-level as a temporary workaround.

Fix this in Url Media Uploader Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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