CVE-2024-2663
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 · uneditedThe ZD YouTube FLV Player plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 1.2.6 via the $_GET['image'] parameter. This makes it possible for unauthenticated attackers 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 confidenceThe ZD YouTube FLV Player WordPress plugin up to version 1.2.6 lacks proper validation of the $_GET['image'] parameter, allowing unauthenticated attackers to supply arbitrary URLs that the server will request. This SSRF flaw enables attackers to interact with internal services, query internal APIs, or port scan internal network infrastructure.
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
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the ZD YouTube FLV Player plugin installationInspect the WordPress plugins directory at wp-content/plugins/ for a folder named 'zd-youtube-flv-player' or similar containing the plugin filesAffected if The plugin folder exists in the WordPress plugins directory
-
Identify the installed plugin versionOpen the plugin's main PHP file or readme.txt and locate the version header (typically in the plugin comment block at the top of the main file)Affected if The version is 1.2.6 or earlier (any version up to and including 1.2.6)
-
Confirm the plugin is activeQuery the WordPress database table wp_options for option_name='active_plugins', or use the WordPress admin interface to check if ZD YouTube FLV Player appears in the list of active pluginsAffected if The plugin appears in the active plugins list
-
Verify the vulnerable parameter is accessibleTest whether the image parameter can be passed in a request by observing the plugin code for $_GET['image'] usage - check the PHP files within the plugin for 'image' GET parameter handlingAffected if The plugin code processes the 'image' parameter from $_GET without validating it is a local or trusted resource
A defender is affected if the ZD YouTube FLV Player plugin version 1.2.6 or earlier is installed and active on their WordPress site, with the vulnerable 'image' parameter handler accessible to unauthenticated users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to the latest version of the plugin if available, or implement allowlist-based validation for the 'image' parameter to restrict URLs to trusted domains only.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2663 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2663 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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