dbcve.org
AvideoApplication · Wwbn

CVE-2020-37172

CRITICAL · 9.8 CVSS v3.1 Published 2026-02-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
AVideo Platform 8.1 contains a cross-site request forgery vulnerability that allows attackers to reset user passwords by exploiting the password recovery mechanism. Attackers can craft malicious requests to the recoverPass endpoint using the user's recovery token to change account credentials without authentication.

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

AVideo Platform 8.1 has a CSRF vulnerability in its password recovery mechanism. Attackers can craft malicious requests to the recoverPass endpoint using a victim's recovery token to reset the account password without authentication, leading to complete account takeover.

MitigationImplement anti-CSRF tokens and validate the origin/referer header on the recoverPass endpoint. Additionally, require additional verification steps (such as email confirmation or CAPTCHA) for password changes.

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
AvideoApplication
Affected:= 8.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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 installed Avideo version
    Check the version.php file or admin panel for the running Avideo version. Common paths include /version.php or look for version information in the admin dashboard under 'About' or 'System Info'.
    Affected if The installed version is exactly 8.1 (Wwbn Avideo = 8.1)
  2. Locate the recoverPass endpoint
    Check if the file 'recoverPass.php' or similar password recovery script exists in the web root or /plugin directory. Search for files containing 'recoverPass' in the codebase.
    Affected if The recoverPass functionality is present and accessible on the server
  3. Verify anti-CSRF token implementation
    Inspect the recoverPass.php or password recovery handler code. Look for token validation logic using $_SESSION, $_POST['csrf_token'], or similar token verification. Check if the form includes a hidden CSRF token field.
    Affected if No anti-CSRF token is generated, stored, or validated in the password recovery code
  4. Check referer/origin header validation
    Review the password recovery handler for server-side checks of $_SERVER['HTTP_REFERER'] or $_SERVER['HTTP_ORIGIN'] to validate the request origin.
    Affected if The recoverPass endpoint lacks origin/referer header validation before processing password reset requests

A user is affected if running Wwbn Avideo version 8.1 with an accessible recoverPass endpoint that lacks anti-CSRF tokens and origin/referer validation.

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

Implement anti-CSRF tokens and validate the origin/referer header on the recoverPass endpoint. Additionally, require additional verification steps (such as email confirmation or CAPTCHA) for password changes.

Recommended fix Moderate confidence

AVideo Platform 8.2 or later stable release

  1. 1. Backup your current AVideo Platform installation and database before proceeding with any upgrade
  2. 2. Navigate to the official AVideo GitHub repository (github.com/WWBN/AVideo) to obtain the latest stable release
  3. 3. Download the fixed release version (8.2 or later) that addresses the CSRF vulnerability in the password recovery mechanism
  4. 4. Extract the new version files to your server, preserving your configuration files (e.g., /videos/configuration.php)
  5. 5. Update your database by running any included SQL migration scripts
  6. 6. Verify the password recovery endpoint now includes proper CSRF token validation
  7. 7. Test the password recovery flow to confirm the vulnerability is mitigated
  8. 8. Clear any server-side caches and verify the application functions correctly
Caveat Minor version upgrades typically have minimal breaking changes, but always review release notes before upgrading production systems

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

Fix this in Avideo 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-2020-37172 — 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-2020-37172 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