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

CVE-2025-49430

HIGH · 7.2 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 →
81/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
Server-Side Request Forgery (SSRF) vulnerability in FWDesign Ultimate Video Player fwduvp allows Server Side Request Forgery.This issue affects Ultimate Video Player: from n/a through <= 10.1.

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 · moderate confidence

Server-Side Request Forgery (SSRF) vulnerability in FWDesign Ultimate Video Player (fwduvp) versions through 10.1 allows remote attackers to induce the server to make arbitrary requests to internal or external resources. This occurs due to insufficient validation of user-controlled URL parameters used for fetching video content.

MitigationImplement strict allowlist-based URL validation for all remote resource endpoints, restrict server-side request capabilities to trusted domains, and apply network segmentation to limit the impact of potential SSRF exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm fwduvp installation
    Search your web server for files or directories containing 'fwduvp', 'Ultimate Video Player', or the plugin/component name used by your CMS (WordPress, Joomla, etc.)
    Affected if The fwduvp software is found on the server
  2. Identify installed version
    Check plugin metadata (version file, header comments, admin panel, or database) and compare to 10.1
    Affected if The installed version is 10.1 or lower
  3. Verify remote URL video fetching is enabled
    Inspect the plugin configuration settings for options that allow video sources from external URLs (such as 'URL', 'Remote', or 'Stream' input fields)
    Affected if The plugin is configured to accept remote URLs as video sources
  4. Check for user-accessible video endpoint
    Locate the request handler that processes video URL parameters (typically in php files handling ajax requests or direct video playback endpoints)
    Affected if A publicly accessible endpoint accepts URL parameters for video content without strict validation

You are affected if fwduvp version 10.1 or lower is installed and the remote URL video fetching feature is enabled and accessible to users.

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

Implement strict allowlist-based URL validation for all remote resource endpoints, restrict server-side request capabilities to trusted domains, and apply network segmentation to limit the impact of potential SSRF exploitation.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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