← Back to results
Vulnerability record · public intelligence
CVE-2026-33038
HIGH

AVideo affected by unauthenticated application takeover via exposed web installer on uninitialized deployments

Published Mar 20, 2026 · Updated Oct 23, 2026 · Also known as GHSA-2f9h-23f7-8gcx

Severity · CVSSHIGH · 8.1
Known exploitationNot listed
EPSS / likelihood0.54%
QFinch risk score10 / 100

Original summary

Normalized public record · Updated Oct 23, 2026

AVideo affected by unauthenticated application takeover via exposed web installer on uninitialized deployments

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

## Summary The `install/checkConfiguration.php` endpoint performs full application initialization — database setup, admin account creation, and configuration file write — from unauthenticated POST input. The only guard is checking whether `videos/configuration.php` already exists. On uninitialized deployments, any remote attacker can complete the installation with attacker-controlled credentials and an attacker-controlled database, gaining full administrative access.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

CVENVDOSVEPSSGHSA
SSVC priority
MEDIUM
Confidence
10%
Aliases
GHSA-2f9h-23f7-8gcx

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. Security advisory ↗
  2. Patch commit ↗

Record history

Published Mar 20, 2026 · Last refreshed Oct 23, 2026