dbcve.org
Revive AdserverApplication

CVE-2026-50745

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-26
Fix available
A fix is available. Upgrade to 6.0.8 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 8 weeks old

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 missing sanitisation vulnerability exists with user input in the stats-video.php script. The way URLs to this script were constructed did not follow best practices, and the output of the Smarty custom helper function url was neither properly encoded nor sanitised, allowing user‑supplied input to be reflected without escaping.

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

This is a reflected Cross-Site Scripting (XSS) vulnerability in the stats-video.php script where user-supplied input is reflected without proper sanitization. The Smarty custom helper function 'url' outputs user input without encoding or escaping, allowing malicious scripts to be injected via crafted URLs and executed in victim browsers.

MitigationImplement proper output encoding/sanitization in the Smarty template's url helper function to ensure all user-supplied input is escaped before rendering. Apply context-aware encoding based on where the output is being placed (HTML attribute, URL parameter, etc.).

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
Revive AdserverApplication
Affected:< 6.0.8

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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify Revive Adserver installation and version
    Locate the Revive Adserver installation directory and check the version file (typically version.php or similar) to determine the installed version number
    Affected if Installed version is less than 6.0.8
  2. Locate the stats-video.php script
    Search for stats-video.php within the Revive Adserver web directory structure
    Affected if The stats-video.php script exists in the installation
  3. Examine the Smarty template for the 'url' helper function
    Inspect the Smarty template files that handle URL generation in the stats-video.php context, specifically looking for custom 'url' helper function implementations that output user input without encoding
    Affected if The 'url' helper function outputs raw user-supplied input without proper escaping or encoding
  4. Test for reflected XSS via URL parameters
    If the script is accessible, carefully inspect HTTP requests and responses to see if URL parameters are reflected in the output without sanitization (this is a manual review step, not an active exploit)
    Affected if User-supplied URL parameters are reflected in the response without HTML encoding

A user is affected if they are running Revive Adserver version less than 6.0.8 AND the stats-video.php script with the vulnerable Smarty 'url' helper function is present and accessible in their environment.

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 6.0.8 or later
Fixed in 6.0.8
Interim mitigation

Implement proper output encoding/sanitization in the Smarty template's url helper function to ensure all user-supplied input is escaped before rendering. Apply context-aware encoding based on where the output is being placed (HTML attribute, URL parameter, etc.).

Recommended fix Moderate confidence

6.0.8

  1. 1. Create a complete backup of the Revive Adserver database and all files
  2. 2. Download Revive Adserver version 6.0.8 from the official project repository (reviveadserver.org)
  3. 3. Extract the upgrade package to a temporary location
  4. 4. Follow the official upgrade instructions to apply the update, replacing the existing files
  5. 5. Clear any caches and verify the upgrade by accessing the admin interface
  6. 6. Confirm the version displays as 6.0.8 to ensure the patch was applied

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

Fix this in Revive Adserver 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 the upgrade done

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-2026-50745 — 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-2026-50745 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