dbcve.org
AvideoApplication · Wwbn

CVE-2023-47862

CRITICAL · 9.8 CVSS v3.1 Published 2024-01-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
A local file inclusion vulnerability exists in the getLanguageFromBrowser functionality of WWBN AVideo dev master commit 15fed957fb. A specially crafted HTTP request can lead to arbitrary code execution. An attacker can send a series of HTTP requests to trigger this vulnerability.

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

A local file inclusion vulnerability in WWBN AVideo's getLanguageFromBrowser function allows attackers to manipulate HTTP requests to include arbitrary files from the server filesystem. The vulnerability stems from insufficient validation of user-controlled input (likely Accept-Language headers or similar browser parameters) used to determine which language file to load. This can be chained with path traversal sequences to access sensitive system files or, when combined with log poisoning or inclusion of writable PHP files, achieve arbitrary code execution.

MitigationImplement strict whitelist-based validation for language parameters, use basename() and realpath() to sanitize file paths and prevent directory traversal, and disable allow_url_include in PHP configuration. Alternatively, replace dynamic file inclusion with a predefined language mapping array.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AvideoApplication
Affected:= 15fed957fb

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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 AVideo installation
    Locate the AVideo web application files on the server. Search for index.php or common AVideo directory structures. If using a package manager or control panel, verify the installed package name and location.
    Affected if WWBN AVideo software is present on the server
  2. Determine AVideo version
    Check for version information in the AVideo installation. Look for a version file, changelog, or git repository (.git directory) that may contain commit hash 15fed957fb. Compare your version against the affected commit.
    Affected if The installed version matches commit 15fed957fb or is derived from this specific commit
  3. Locate getLanguageFromBrowser function
    Search the AVideo source code for the getLanguageFromBrowser function definition. Common locations may include language-related files or helper utilities. Use grep or similar tools: grep -r 'function getLanguageFromBrowser' .
    Affected if The getLanguageFromBrowser function exists in the codebase and is accessible via HTTP requests
  4. Verify Accept-Language header handling
    Inspect the getLanguageFromBrowser function code to confirm it processes the Accept-Language HTTP header or similar browser-provided language parameters. Check if user input is used directly in file inclusion operations without proper sanitization.
    Affected if The function processes Accept-Language headers without validating for path traversal sequences like ../ or null bytes
  5. Test for LFI via language parameter
    Send an HTTP request to any AVideo page with a manipulated Accept-Language header containing path traversal, such as Accept-Language: ../../../../etc/passwd. Observe if the response includes content from the targeted system file.
    Affected if The server responds with content from files outside the intended language directory, confirming the LFI vulnerability is exploitable

The environment is affected if running AVideo at commit 15fed957fb and the getLanguageFromBrowser function processes Accept-Language headers without path traversal validation, allowing unauthorized file access.

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 strict whitelist-based validation for language parameters, use basename() and realpath() to sanitize file paths and prevent directory traversal, and disable allow_url_include in PHP configuration. Alternatively, replace dynamic file inclusion with a predefined language mapping array.

Fix this in Avideo Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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