dbcve.org
Stream Video PlayerApplication · Rodrigo Polo

CVE-2013-2706

MEDIUM · 6.8 CVSS v2.0 Published 2014-04-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
Cross-site request forgery (CSRF) vulnerability in the Stream Video Player plugin 1.4.0 for WordPress allows remote attackers to hijack the authentication of administrators for requests that change plugin settings via unspecified vectors.

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

This is a Cross-Site Request Forgery (CSRF) vulnerability in the Stream Video Player WordPress plugin version 1.4.0. The plugin lacks proper anti-CSRF token validation on its settings forms, allowing remote attackers to craft malicious requests that trick authenticated administrators into unknowingly modifying plugin settings.

MitigationImplement WordPress nonces (wp_create_nonce/wp_verify_nonce) on all plugin settings forms and their processing handlers to validate request authenticity and prevent CSRF attacks.

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
Stream Video PlayerApplication
Affected:= 1.4.0

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
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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 Stream Video Player plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Stream Video Player' by Rodrigo Polo in the installed plugins list, or inspect the /wp-content/plugins/stream-video-player directory
    Affected if plugin is not present in the WordPress installation
  2. Confirm installed version is 1.4.0
    In WordPress admin > Plugins > Installed Plugins, click on the Stream Video Player plugin to view its details, or open the main plugin file (stream-video-player.php) and look for the 'Version' header comment
    Affected if version is 1.4.0 exactly
  3. Inspect settings form code for nonce validation
    Open the main plugin PHP file and locate the settings form handler functions. Search for wp_verify_nonce, wp_create_nonce, or check_admin_referer calls within the form processing logic
    Affected if no nonce validation functions are found in settings form handlers

User is affected if Stream Video Player version 1.4.0 is installed and its settings forms lack WordPress nonce validation checks.

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 WordPress nonces (wp_create_nonce/wp_verify_nonce) on all plugin settings forms and their processing handlers to validate request authenticity and prevent CSRF attacks.

Fix this in Stream Video Player 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 help mitigating

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-2013-2706 — 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-2013-2706 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