dbcve.org
AvideoApplication · Wwbn

CVE-2023-48730

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 cross-site scripting (xss) vulnerability exists in the navbarMenuAndLogo.php user name functionality of WWBN AVideo dev master commit 15fed957fb. A specially crafted HTTP request can lead to arbitrary Javascript execution. An attacker can get a user to visit a webpage 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 · moderate confidence

A stored cross-site scripting (XSS) vulnerability exists in the navbarMenuAndLogo.php file of WWBN AVideo, specifically in the user name functionality. The vulnerability allows attackers to inject malicious JavaScript through a specially crafted HTTP request. When other users view the affected page, the injected script executes in their browsers, potentially enabling session hijacking, credential theft, or other client-side attacks.

MitigationImplement proper input validation and output encoding/escaping for all user-supplied data in the username field. Use context-appropriate encoding when rendering user input in HTML, and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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
    Locate the AVideo web application files on the server. Identify the directory where the CMS is installed.
    Affected if The system is running WWBN AVideo software
  2. Identify installed version
    Check the AVideo version information. Common methods include: looking for a version file in the installation directory, checking git commit information if using git, or accessing the admin panel version display.
    Affected if The installed version matches commit 15fed957fb or the software has not been updated beyond this specific commit
  3. Locate vulnerable file
    Search for the file navbarMenuAndLogo.php within the AVideo installation directory.
    Affected if The file navbarMenuAndLogo.php exists in the installation
  4. Verify username functionality is active
    Determine if the user registration or profile username feature is enabled and accessible. This may require checking the system configuration or attempting to access user-related pages.
    Affected if The username functionality in the navbarMenuAndLogo.php file is accessible to users
  5. Check for existing XSS protections
    Inspect the navbarMenuAndLogo.php code for input validation or output encoding functions around the username display area. Look for functions like htmlspecialchars, htmlentities, or similar sanitization routines.
    Affected if No input validation or output encoding is found for the username field in the vulnerable file

You are affected if you are running WWBN AVideo at exactly commit 15fed957fb with the username functionality enabled and no XSS protections present in navbarMenuAndLogo.php.

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 proper input validation and output encoding/escaping for all user-supplied data in the username field. Use context-appropriate encoding when rendering user input in HTML, and consider implementing Content Security Policy (CSP) headers as a defense-in-depth measure.

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-48730 — 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-48730 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