dbcve.org
AvideoApplication · Wwbn

CVE-2026-45610

MEDIUM · 6.5 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to after 29.0 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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
WWBN AVideo is an open source video platform. In 29.0 and earlier, there is a cross-site request forgery vulnerability on the 2FA toggle. plugin/LoginControl/set.json.php accepts POST type=set2FA value=false, calls LoginControl::setUser2FA(User::getId(), false) on the session-authenticated user, and returns. There is no forbidIfIsUntrustedRequest() call, no isTokenValid() check, no X-CSRF-Token/SameSite enforcement, and no re-authentication step. A cross-origin page that the victim visits while logged into the AVideo dashboard issues the POST via a hidden form (or fetch without credentials:"omit") and disables the victim's 2FA in one request.

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

CSRF vulnerability in AVideo's 2FA toggle endpoint (plugin/LoginControl/set.json.php) allows attackers to disable victims' two-factor authentication. The endpoint lacks forbidIfIsUntrustedRequest(), isTokenValid() checks, CSRF tokens, SameSite cookie enforcement, and re-authentication requirements. Attackers can exploit this via a hidden form or credential-less fetch from a malicious page while the victim has an active AVideo session.

MitigationImplement synchronizer token pattern (anti-CSRF tokens) for the 2FA toggle endpoint and add SameSite=Strict cookie attributes or require re-authentication before allowing security-sensitive changes like 2FA configuration.

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:<= 29.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
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 installed AVideo version
    Locate the version file or check the admin dashboard for the exact AVideo version number. Common locations include a version.php file or the About section in the admin panel.
    Affected if The installed version is 29.0 or lower (any version up to and including 29.0).
  2. Confirm LoginControl plugin is enabled
    Check the plugins directory or admin panel to verify the LoginControl plugin is installed and active.
    Affected if The LoginControl plugin is installed and enabled on the AVideo installation.
  3. Locate the vulnerable endpoint file
    Navigate to the file plugin/LoginControl/set.json.php in the AVideo web root and verify it exists.
    Affected if The file plugin/LoginControl/set.json.php exists on the server.
  4. Inspect endpoint for CSRF protection
    Open plugin/LoginControl/set.json.php and search for function calls: forbidIfIsUntrustedRequest() or isTokenValid() within the code that handles the set2FA type parameter.
    Affected if The endpoint processes type=set2FA requests WITHOUT calling forbidIfIsUntrustedRequest() or isTokenValid() for CSRF validation.
  5. Check session cookie configuration
    Inspect the PHP session configuration or cookies for SameSite attribute. Look for session.cookie_samesite setting in php.ini or session cookie headers.
    Affected if Session cookies lack SameSite=Strict or SameSite=Lax attributes, or no X-CSRF-Token header is required.

A user is affected if they run AVideo version 29.0 or lower, have the LoginControl plugin enabled, and the set.json.php endpoint lacks CSRF token validation (forbidIfIsUntrustedRequest or isTokenValid) when processing set2FA requests.

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 29.0
Interim mitigation

Implement synchronizer token pattern (anti-CSRF tokens) for the 2FA toggle endpoint and add SameSite=Strict cookie attributes or require re-authentication before allowing security-sensitive changes like 2FA configuration.

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 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-2026-45610 — 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-2026-45610 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