How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, and whether compensating controls exist. A Medium CVSS on an exposed production system can be more urgent than a Critical on an isolated non-production host.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

Recurring findings usually come from incomplete asset discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host.

Q: How do we prioritize remediation without burning out the team?

Use a repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.

352,262

Total vulnerabilities in the database

CVE-2026-33684 — wwbn / avideo

Missing Authorization

Summary

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. Any anonymous user who can solve a CAPTCHA can self-grant elevated permissions during account registration.

Details

The authentication check in set_api_signUp (plugin/API/API.php:4222) allows either a valid APISecret (admin-level credential) or a solved CAPTCHA (anonymous access):

// plugin/API/API.php:4222-4232
if ($obj-&gt;APISecret !== @$_REQUEST[&#039;APISecret&#039;]) {
    if(empty($_REQUEST[&#039;captcha&#039;])){
        return new ApiObject(&quot;Captcha is required&quot;);
    }
    require_once $global[&#039;systemRootPath&#039;] . &#039;objects/captcha.php&#039;;
    $valid = Captcha::validation($_REQUEST[&#039;captcha&#039;]);
    if(!$valid){
        return new ApiObject(&quot;Captcha is wrong, reload it and try again&quot;);
    }
}

After this check, both code paths (APISecret and CAPTCHA) reach the privilege parameter handling unconditionally:

// plugin/API/API.php:4238-4249
if (isset($_REQUEST[&#039;emailVerified&#039;])) {
    $global[&#039;emailVerified&#039;] = intval($_REQUEST[&#039;emailVerified&#039;]);
}
if (isset($_REQUEST[&#039;canCreateMeet&#039;])) {
    $global[&#039;canCreateMeet&#039;] = intval($_REQUEST[&#039;canCreateMeet&#039;]);
}
if (isset($_REQUEST[&#039;canStream&#039;])) {
    $global[&#039;canStream&#039;] = intval($_REQUEST[&#039;canStream&#039;]);
}
if (isset($_REQUEST[&#039;canUpload&#039;])) {
    $global[&#039;canUpload&#039;] = intval($_REQUEST[&#039;canUpload&#039;]);
}

These $global values are then consumed by User::save() (objects/user.php:829-840), which overrides the user object's permission fields:

// objects/user.php:829-840
if (isset($global[&#039;emailVerified&#039;])) {
    $this-&gt;emailVerified = $global[&#039;emailVerified&#039;];
}
if (isset($global[&#039;canCreateMeet&#039;])) {
    $this-&gt;canCreateMeet = $global[&#039;canCreateMeet&#039;];
}
if (isset($global[&#039;canStream&#039;])) {
    $this-&gt;canStream = $global[&#039;canStream&#039;];
}
if (isset($global[&#039;canUpload&#039;])) {
    $this-&gt;canUpload = $global[&#039;canUpload&#039;];
}

Note that even though userCreate.json.php:90 sets canUpload from the site's default configuration, User::save() subsequently overrides it with the attacker-controlled $global value.

The codebase already uses self::isAPISecretValid() to guard admin-only operations in other API methods (e.g., lines 294, 991, 1664, 2150), but this check is missing for the privilege parameters in set_api_signUp.

PoC

# Step 1: Get a CAPTCHA token
# (Navigate to the signup page in a browser, solve the CAPTCHA, capture the token)

# Step 2: Register with elevated privileges
curl -X POST &#039;https://target/plugin/API/set.json.php&#039; \
  -d &#039;APIName=signUp&#039; \
  -d &#039;user=attacker&#039; \
  -d &#039;pass=Password123!&#039; \
  -d &#039;[email protected]&#039; \
  -d &#039;name=Attacker&#039; \
  -d &#039;captcha=VALID_CAPTCHA_TOKEN&#039; \
  -d &#039;emailVerified=1&#039; \
  -d &#039;canUpload=1&#039; \
  -d &#039;canStream=1&#039; \
  -d &#039;canCreateMeet=1&#039;

# Expected: Account created with default (restricted) permissions
# Actual: Account created with upload, stream, and meet permissions enabled,
#         plus email marked as verified

# Step 3: Verify elevated permissions by logging in and checking profile
curl -X POST &#039;https://target/plugin/API/set.json.php&#039; \
  -d &#039;APIName=signIn&#039; \
  -d &#039;user=attacker&#039; \
  -d &#039;pass=Password123!&#039;
# Response will show canUpload=1, canStream=1, canCreateMeet=1, emailVerified=1

Impact

Email verification bypass: Attackers can mark their accounts as email-verified without owning the email address, bypassing any email-gated functionality
Unauthorized upload access: Self-granted upload permissions allow uploading potentially malicious video content to the platform
Unauthorized streaming access: Self-granted streaming permissions allow unauthorized live streaming
Unauthorized meeting creation: Self-granted meet permissions allow creating meetings on the platform
Policy bypass: Platform administrators who intentionally restrict these permissions for new users (e.g., requiring manual approval before granting upload rights) have their access controls circumvented

Recommended Fix

Wrap the privilege parameter handling in an isAPISecretValid() check so that only admin-authenticated requests can set these values:

// plugin/API/API.php — replace lines 4238-4249 with:
if (self::isAPISecretValid()) {
    if (isset($_REQUEST[&#039;emailVerified&#039;])) {
        $global[&#039;emailVerified&#039;] = intval($_REQUEST[&#039;emailVerified&#039;]);
    }
    if (isset($_REQUEST[&#039;canCreateMeet&#039;])) {
        $global[&#039;canCreateMeet&#039;] = intval($_REQUEST[&#039;canCreateMeet&#039;]);
    }
    if (isset($_REQUEST[&#039;canStream&#039;])) {
        $global[&#039;canStream&#039;] = intval($_REQUEST[&#039;canStream&#039;]);
    }
    if (isset($_REQUEST[&#039;canUpload&#039;])) {
        $global[&#039;canUpload&#039;] = intval($_REQUEST[&#039;canUpload&#039;]);
    }
}

Published: Jun 22, 2026
Updated: Jun 23, 2026
CVE: CVE-2026-33684
GHSA: GHSA-8j8m-p79x-g4jm
Severity: Medium
Exploit:
CISA KEV:

CVSS v3:

Severity: Medium
Score: 5.3
AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

CWEs:

CWE-862

Affected Software
References

Software	From	Fixed in
wwbn / avideo	-	29.0

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.