dbcve.org
Revive AdserverApplication

CVE-2026-50740

MEDIUM · 5.4 CVSS v3.1 Published 2026-06-26
Fix available
A fix is available. Upgrade to 6.0.8 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable 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 of user input in the zone-include.php script exists in Revive Adserver 6.0.7 and earlier. A low‑privileged user could exploit the refresh parameter of the iFrame invocation tag to perform reflected XSS attacks.

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 reflected XSS vulnerability in Revive Adserver's zone-include.php script allows low-privileged users to inject malicious JavaScript through the refresh parameter of the iFrame invocation tag due to missing input sanitization.

MitigationUpgrade to a patched version of Revive Adserver, or implement proper input validation and sanitization on the refresh parameter in zone-include.php to neutralize malicious script execution.

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
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. Locate Revive Adserver installation
    Search for the 'zone-include.php' file in your web root directories, typically found under /www/ or /htdocs/ in paths like /ads/ or /adserver/
    Affected if The zone-include.php file exists in your web directory structure
  2. Identify installed Revive Adserver version
    Check the version file (usually named 'version.php' in the '/var/' or '/lib/' directory of the installation) or log into the admin dashboard and view the system information page
    Affected if The version is displayed as lower than 6.0.8 or the file shows a version number < 6.0.8
  3. Verify zone-include.php handles refresh parameter
    Open zone-include.php and search for code that processes the 'refresh' parameter, typically using $_GET['refresh'] or $_REQUEST['refresh'] without sanitization functions like htmlspecialchars() or paramaterized queries
    Affected if The script retrieves the refresh parameter directly from user input without applying input validation or output encoding
  4. Confirm iFrame invocation tag is accessible
    Check if the affected zone-include.php is accessible via web browser (e.g., /ads/zone-include.php?zoneid=1&refresh=...) and that low-privileged users have permission to generate invocation tags
    Affected if The vulnerable script is web-accessible and users with low privileges can create or modify invocation tags

You are affected if Revive Adserver version is below 6.0.8 and the zone-include.php script processes the refresh parameter without sanitization, allowing injected JavaScript through the iFrame invocation tag.

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

Upgrade to a patched version of Revive Adserver, or implement proper input validation and sanitization on the refresh parameter in zone-include.php to neutralize malicious script execution.

Recommended fix Moderate confidence

6.0.8

  1. Download Revive Adserver version 6.0.8 or later from the official repository
  2. Backup your current Revive Adserver installation and database
  3. Extract the new version files
  4. Replace the existing installation files with the new version
  5. Run any database migration scripts included in the upgrade
  6. Verify the zone-include.php script has been updated in the new version
  7. Test that the XSS vulnerability in the refresh parameter is no longer exploitable

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

Fix this in Revive Adserver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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