LiveActive security incident?Get immediate response
CVE Record

CVE-2023-47862: A local file inclusion vulnerability exists in the getLanguageFromBrowser functionality of WWBN AVideo dev...

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2023-47862 is a critical flaw in WWBN AVideo’s browser-language handling. The public record says a specially crafted HTTP request can trigger local file inclusion and lead to arbitrary code execution. This is high business urgency for any exposed AVideo instance matching the affected development commit.

Executive priority

Treat as urgent if AVideo is deployed, especially on the public internet. The vulnerability is rated critical and may allow full system compromise, but the supplied sources do not prove active exploitation.

Technical view

The issue is a CWE-73 external control of file name or path weakness in getLanguageFromBrowser in WWBN AVideo dev master commit 15fed957fb. The CVSS 3.1 score is 9.8 because exploitation is network-reachable, unauthenticated, low complexity, and can affect confidentiality, integrity, and availability.

Likely exposure

Evidence only names WWBN AVideo dev master commit 15fed957fb. Organizations running that commit, downstream builds from it, or unverified custom deployments should treat exposure as plausible until checked.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Talos and CVE data describe crafted HTTP requests as the attack path, but no confirmed exploitation-in-the-wild signal is provided.

Researcher notes

Do not broaden affected scope beyond AVideo dev master commit 15fed957fb without vendor evidence. The available data supports LFI leading to code execution, CVSS 9.8, CWE-73, and unauthenticated network reachability; patch details are not included in the bundle.

Mitigation direction

  • Identify whether any AVideo deployment matches or derives from commit 15fed957fb.
  • Check WWBN and Talos guidance for a fixed version or official remediation.
  • Restrict public access to affected AVideo instances until exposure is resolved.
  • Prioritize patching or replacement for internet-facing instances.
  • Review web logs for unusual language or localization-related request patterns.

Validation and detection

  • Inventory all AVideo versions, commits, containers, and custom forks in use.
  • Compare deployed code lineage against dev master commit 15fed957fb.
  • Confirm whether getLanguageFromBrowser exists in the deployed build.
  • Verify vendor-fixed code or compensating access controls are present.
  • Document whether each instance is internet-facing or internally restricted.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-73: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-47862 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2023-47862Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
WWBNAVideodev master commit 15fed957fbListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-73 · source CWE mapping

External Control of File Name or Path

External Control of File Name or Path represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.