dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-56346

MEDIUM · 6.5 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 →
74/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
AVideo through version 25.0 contains an authentication bypass vulnerability in the decryptMessage.json.php endpoint that allows unauthenticated users to decrypt PGP messages. Remote attackers can submit private keys, ciphertext, and passphrases to perform server-side decryption without credentials, exposing key material to logs and enabling resource exhaustion attacks.

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

AVideo through version 25.0 has an authentication bypass in the decryptMessage.json.php endpoint that allows unauthenticated attackers to submit private keys, ciphertext, and passphrases for server-side PGP decryption. This exposes sensitive key material to application logs and enables resource exhaustion through repeated decryption requests.

MitigationRestrict the decryptMessage.json.php endpoint to authenticated users only, implement proper authorization checks before processing any cryptographic operations, sanitize all log output to exclude sensitive key material, and add rate limiting to prevent resource exhaustion attacks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

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 installation and version
    Locate the AVideo installation directory and check the version file (typically includes a version.php, CHANGELOG.md, or similar version indicator). Compare the installed version against 'through version 25.0' - any version at or below 25.0 is potentially affected.
    Affected if AVideo version is 25.0 or lower, as versions up to and including 25.0 contain the vulnerable endpoint.
  2. Locate the decryptMessage.json.php endpoint
    Search for the file decryptMessage.json.php within the AVideo web root directory. Common paths may include /plugin/Chat2/, /include/, or /api/ directories. Identify its full filesystem path.
    Affected if The file exists in the AVideo installation, indicating the vulnerable endpoint is present.
  3. Verify unauthenticated access to the endpoint
    Using a tool like curl, send a POST request to the decryptMessage.json.php endpoint without providing any session cookie, authentication token, or login credentials. Example: curl -X POST https://your-site.com/decryptMessage.json.php -d 'test=data'
    Affected if The endpoint responds with a valid HTTP status (200, 400, 500, etc.) rather than rejecting the request with an authentication error (401, 403, or redirect to login), confirming the authentication bypass exists.
  4. Inspect application logs for key material exposure
    Examine AVideo's application log files (commonly found in /videos/logs/, /tmp/, or a dedicated logs directory within the installation). Search for patterns indicating PGP private keys, passphrases, or ciphertext appearing in plaintext log entries.
    Affected if Log files contain plaintext private keys, passphrase strings, or ciphertext that were submitted through the decryptMessage.json.php endpoint, indicating sensitive material is being logged.
  5. Check for rate limiting on decryption endpoints
    Review web server configuration (Apache .htaccess, Nginx config) and any AVideo security settings for rate limiting rules targeting the decryptMessage.json.php endpoint or related cryptographic functions. Also observe server response times under repeated request loads.
    Affected if No rate limiting is configured for the decryption endpoint, making the system vulnerable to resource exhaustion through repeated requests.

A user is affected if running AVideo version 25.0 or lower with the decryptMessage.json.php endpoint accessible without authentication and without rate limiting, potentially evidenced by sensitive key material in logs.

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

Restrict the decryptMessage.json.php endpoint to authenticated users only, implement proper authorization checks before processing any cryptographic operations, sanitize all log output to exclude sensitive key material, and add rate limiting to prevent resource exhaustion attacks.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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