dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-33684

MEDIUM · 5.3 CVSS v3.1 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 5 weeks old

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. Prior to version 29.0, Privilege Escalation is possible through unguarded permission parameters in signUp API, which allows any user who can solve a CAPTCHA to self-grant elevated permissions during account registration. The set_api_signUp method in the API plugin accepts emailVerified, canUpload, canStream, and canCreateMeet parameters from user-supplied input and applies them to newly created accounts without verifying that the request was authenticated with a valid APISecret. By self-granting account attributes, attackers can mark their own accounts as email-verified without owning the address (bypassing email-gated functionality) and award themselves upload, streaming, and meeting-creation permissions, circumventing administrator access controls that intentionally restrict these capabilities for new users. This issue has been fixed in version 29.0

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 set_api_signUp method in AVideo's API plugin accepts user-supplied permission parameters (emailVerified, canUpload, canStream, canCreateMeet) and applies them to newly created accounts without validating that the request included a valid APISecret, allowing any user who solves CAPTCHA to self-grant elevated privileges.

MitigationUpgrade to AVideo version 29.0 which includes proper APISecret validation for permission parameters in the signUp API.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 admin dashboard 'About' page to determine the current AVideo installation version
    Affected if version is lower than 29.0 (the fixed release)
  2. Locate API plugin directory
    Check for the presence of the plugin directory (usually in Plugin or plugin folder) containing API-related files, particularly the set_api_signUp method file
    Affected if API plugin is installed and accessible
  3. Verify API signup endpoint accessibility
    Examine the API plugin configuration file or test accessing the signup API endpoint (typically /plugin/API/signUp.json or similar path)
    Affected if the signUp API endpoint responds without requiring valid APISecret validation
  4. Check permission parameter handling
    Review the set_api_signUp method code in the API plugin to see if permission parameters (emailVerified, canUpload, canStream, canCreateMeet) are processed without APISecret validation
    Affected if permission parameters can be set without providing a valid APISecret

A user is affected if running AVideo version below 29.0 with the API plugin enabled and the signUp endpoint accessible without proper APISecret validation for permission parameters.

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

Upgrade to AVideo version 29.0 which includes proper APISecret validation for permission parameters in the signUp API.

Recommended fix High confidence

AVideo version 29.0

  1. Backup the current AVideo installation and database before proceeding with the upgrade
  2. Download AVideo version 29.0 from the official GitHub repository (github.com/WWBN/AVideo)
  3. Replace the existing AVideo files with the new version 29.0 files
  4. Run any database migration scripts included in the upgrade if applicable
  5. Verify the installation is functioning correctly after the upgrade
  6. Test that the signUp API no longer accepts unauthenticated permission parameters (emailVerified, canUpload, canStream, canCreateMeet)
Caveat Review release notes for version 29.0 to check for any breaking changes or required configuration updates

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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