dbcve.org
AvideoApplication · Wwbn

CVE-2026-45620

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to after 29.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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
WWBN AVideo is an open source video platform. In 29.0 and earlier, objects/mention.json.php has no User::loginCheck() or admin gate. It only has an entry guard: preg_match('/^@/', $_REQUEST['term']) and hard-coded rowCount=10. This enables unauthenticated user enumeration.

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

The objects/mention.json.php endpoint in WWBN AVideo versions 29.0 and earlier lacks proper authentication checks, only enforcing a weak client-side filter that checks if the 'term' parameter begins with '@'. This enables unauthenticated attackers to enumerate valid usernames through the mention functionality.

MitigationImplement proper authentication using User::loginCheck() or an admin gate on the objects/mention.json.php endpoint to prevent unauthenticated access.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 AVideo version
    Locate the version file or header in your AVideo installation - typically found in a version.php file, dashboard about page, or HTTP server headers. Compare the installed version against the affected range <= 29.0.
    Affected if Installed version is 29.0 or lower
  2. Verify vulnerable endpoint exists
    Check if the file objects/mention.json.php exists in your AVideo web root directory.
    Affected if The file objects/mention.json.php exists in the installation
  3. Test endpoint authentication requirement
    Send an HTTP GET request to objects/mention.json.php?term=@test without providing any session cookie, login token, or authentication credentials. Observe the response status and content.
    Affected if The endpoint returns a successful response (200 OK) with JSON data instead of redirecting to a login page or returning an authentication error
  4. Confirm username enumeration is possible
    Send requests with different @terms to the endpoint (e.g., @admin, @user, @test) without authentication. Check if the response reveals whether each username exists in the system.
    Affected if The endpoint reveals valid usernames through different response patterns (e.g., returns user data for valid usernames, empty results for invalid ones) without requiring authentication

If your AVideo version is 29.0 or lower AND the mention.json.php endpoint is accessible without authentication, your installation is affected by this username enumeration vulnerability.

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
Upgrade available Upgrade to a release after 29.0
Interim mitigation

Implement proper authentication using User::loginCheck() or an admin gate on the objects/mention.json.php endpoint to prevent unauthenticated access.

Recommended fix Moderate confidence

Upgrade to AVideo release > 29.0 (check GitHub releases for the specific fixed version)

  1. 1. Backup your current AVideo installation before making any changes
  2. 2. Navigate to your AVideo installation directory
  3. 3. Locate the file objects/mention.json.php
  4. 4. Add User::loginCheck() at the beginning of the file before any processing occurs to require authentication
  5. 5. Alternatively, restrict access to this endpoint by adding an admin gate check
  6. 6. Verify the fix by attempting to access objects/mention.json.php without authentication - it should return an error or require login
  7. 7. Test that legitimate @mention functionality still works for authenticated users
Caveat Adding authentication may break existing integrations that rely on unauthenticated access to mention functionality

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

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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 locally
dbcve dependency scanner

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