dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-56345

HIGH · 8.1 CVSS v3.1 Published 2026-06-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
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 through 29.0 contains an authorization bypass vulnerability in the Meet plugin's uploadRecordedVideo.json.php endpoint that derives the target users_id from the uploaded filename without verification. An attacker with knowledge of the Meet shared secret can craft a malicious file upload with a filename containing an arbitrary users_id to invoke passwordless User->login() and establish an authenticated session as any user including admin. Attackers can obtain the Meet shared secret through path-traversal vulnerabilities or timing attacks against checkToken.json.php, then POST a crafted file to uploadRecordedVideo.json.php with a filename like '1-anything.mp4' to hijack admin sessions and gain full account takeover.

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 Meet plugin's uploadRecordedVideo.json.php endpoint derives the target users_id directly from the uploaded filename without server-side validation or authorization checks. An attacker with the Meet shared secret can craft filenames like '1-anything.mp4' to trigger passwordless User->login() as any user, enabling full account takeover including admin privileges.

MitigationImplement server-side validation ensuring the users_id in the filename matches the authenticated user's session ID, and require proper authorization checks before allowing video uploads. Additionally, rotate the Meet shared secret and remediate the path-traversal/timing attack vulnerabilities in checkToken.json.php.

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/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 if Meet plugin is installed
    Check for the presence of the Meet plugin directory or configuration files in your application (e.g., look for 'meet', 'jitsi', or video conferencing related plugins/modules in your plugin or module directory)
    Affected if The Meet plugin is installed and enabled on the system
  2. Locate the vulnerable upload endpoint
    Check for the existence of uploadRecordedVideo.json.php in the Meet plugin directory (typically at /path/to/meet/uploadRecordedVideo.json.php)
    Affected if The file uploadRecordedVideo.json.php exists in the Meet plugin
  3. Verify Meet shared secret configuration
    Check your Meet plugin configuration for a shared secret setting (often named 'sharedSecret', 'secret', or similar in the plugin config file or database)
    Affected if A Meet shared secret is configured and in use
  4. Test endpoint for users_id validation
    Attempt to access or probe the uploadRecordedVideo.json.php endpoint with a crafted filename containing a different users_id (e.g., '2-anything.mp4' when you are not user 2) and observe if the system accepts it without validating against your session
    Affected if The endpoint accepts filenames with arbitrary users_id values without server-side session validation
  5. Confirm authentication bypass capability
    Verify that using a crafted filename like '1-admin-username.mp4' against the upload endpoint can trigger a login as that user without providing valid credentials
    Affected if The endpoint allows passwordless login as arbitrary users by embedding their users_id in the filename

If the Meet plugin is installed with a configured shared secret and the uploadRecordedVideo.json.php endpoint accepts filenames containing arbitrary users_id values without validating them against the authenticated session, the environment is affected by this CVE.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement server-side validation ensuring the users_id in the filename matches the authenticated user's session ID, and require proper authorization checks before allowing video uploads. Additionally, rotate the Meet shared secret and remediate the path-traversal/timing attack vulnerabilities in checkToken.json.php.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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