dbcve.org
Streaming EngineApplication · Wowza

CVE-2024-52053

CRITICAL · 9.6 CVSS v3.1 Published 2024-11-21
Fix available
A fix is available. Upgrade to 4.9.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Stored Cross-Site Scripting in the Manager component of Wowza Streaming Engine below 4.9.1 allows an unauthenticated attacker to inject client-side JavaScript into the web dashboard to automatically hijack admin accounts.

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 stored cross-site scripting vulnerability exists in the Manager web interface component of Wowza Streaming Engine versions prior to 4.9.1. An unauthenticated attacker can inject malicious JavaScript into the dashboard, which executes when administrators access the compromised interface, enabling session hijacking and admin account takeover.

MitigationUpgrade Wowza Streaming Engine to version 4.9.1 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Manager component and implement Content Security Policy headers as a compensating control.

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
Streaming EngineApplication
Affected:>= 4.3.0, < 4.9.1

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Check Wowza Streaming Engine version
    Locate the Wowza installation directory and find the version information. This is typically available in the [install-dir]/license.txt file, or by accessing the Wowza Streaming Engine Manager web interface and navigating to the Server > About page. Alternatively, check the startup logs or run: java -jar [install-dir]/lib/wowzastreamingengine.jar -version
    Affected if The installed version is 4.3.0 through 4.9.0 (any version >= 4.3.0 but < 4.9.1)
  2. Confirm Manager web interface is accessible
    Verify the Wowza Streaming Engine Manager web interface is running and accessible. This is typically hosted on port 8088 (HTTP) or 8089 (HTTPS). Try accessing http://[server]:8088/manager or https://[server]:8089/manager in a web browser. Check if the Manager service is listed as running in the system processes.
    Affected if The Manager web interface component is accessible (running and responding to requests)
  3. Determine if Manager interface is network-exposed
    Review network configuration to determine if the Manager web interface port (8088/8089) is exposed to untrusted networks. Check firewall rules, reverse proxy configurations, and the [install-dir]/conf/VHost.xml file for listener bindings. Look for any external IP bindings versus localhost-only bindings.
    Affected if The Manager interface is bound to a network interface accessible from untrusted networks (not restricted to localhost or internal networks only)
  4. Check for recent unauthorized access indicators
    Review the Wowza Streaming Engine access logs ([install-dir]/logs/access.log) and manager logs ([install-dir]/logs/wowzastreamingmanager_access.log) for any suspicious requests, particularly around the dashboard or configuration endpoints. Look for unexpected POST requests to dashboard/configuration areas or unusual JavaScript injection patterns in request parameters.
    Affected if Suspicious requests containing script tags or JavaScript code are found in the Manager interface logs

You are affected if Wowza Streaming Engine version is 4.3.0 through 4.9.0 AND the Manager web interface component is accessible to users who could inject content into the dashboard.

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.

dbcve · scoped
Upgrade available Upgrade to 4.9.1 or later
Fixed in 4.9.1
Interim mitigation

Upgrade Wowza Streaming Engine to version 4.9.1 or later to remediate this vulnerability. If immediate patching is not possible, restrict network access to the Manager component and implement Content Security Policy headers as a compensating control.

Recommended fix High confidence

4.9.1 or later

  1. 1. Back up the current Wowza Streaming Engine configuration and any custom settings
  2. 2. Download Wowza Streaming Engine version 4.9.1 or later from the official Wowza website (www.wowza.com)
  3. 3. Stop the Wowza Streaming Engine service before upgrading
  4. 4. Install the updated version (4.9.1 or later) following Wowza's standard upgrade documentation
  5. 5. Restart the Wowza Streaming Engine service
  6. 6. Log in to the Manager web dashboard and verify the upgrade was successful
  7. 7. Monitor the dashboard for any residual XSS indicators and clear browser cache to ensure no stale scripts remain
Caveat Review Wowza release notes for any configuration or compatibility changes between your current version and 4.9.1

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Streaming Engine Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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