dbcve.org
Revive AdserverApplication · Aquaplatform

CVE-2026-21642

MEDIUM · 6.1 CVSS v3.0 Published 2026-01-20
Fix available
A fix is available. Upgrade to after 6.0.4 or later.
See remediation →
68/100
Remediation priority · Elevated
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
HackerOne community member Patrick Lang (7yr) has reported a reflected XSS vulnerability in the `banner-acl.php` and `channel-acl.php` scripts of Revive Adserver. An attacker can craft a specific URL that includes an HTML payload in a parameter. If a logged in administrator visits the URL, the HTML is sent to the browser and malicious scripts would be executed.

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 reflected cross-site scripting (XSS) vulnerability exists in Revive Adserver's banner-acl.php and channel-acl.php scripts. The vulnerability allows an attacker to inject malicious HTML/JavaScript via URL parameters. When a logged-in administrator clicks a crafted URL, the unsanitized parameter value is reflected back in the response and executed in the administrator's browser session.

MitigationImplement input validation and output encoding for all user-supplied parameters in the affected files. Use context-appropriate encoding (HTML entity encoding) when reflecting any parameter values in the HTML response, and validate that input conforms to expected formats before processing.

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.4

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.0/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
    Locate the Revive Adserver installation directory on the web server. Common paths include /var/www/html/revive-adserver, /opt/revive-adserver, or C:\inetpub\revive-adserver. Look for the presence of admin/banner-acl.php and admin/channel-acl.php files.
    Affected if The banner-acl.php and channel-acl.php files exist in the Revive Adserver admin directory and the application is accessible over the network.
  2. Determine installed version
    Check the version by inspecting the file lib/version.php or the file CHANGES.txt in the Revive Adserver root directory. Alternatively, access the admin/login.php page and check any version information displayed in the footer or about page.
    Affected if The installed version is 6.0.4 or any earlier version (6.0.0 through 6.0.4).
  3. Verify admin access is enabled
    Confirm that the Revive Adserver admin interface is accessible. Try accessing the login page at /admin/login.php. Check configuration files (etc/debugging.php or etc/config.inc.php) to confirm admin functionality is not disabled.
    Affected if Administrator login is accessible and active, allowing authenticated sessions to be established.
  4. Confirm vulnerability in banner-acl.php
    Access the banner-acl.php script directly via browser using a logged-in administrator session. Inject a test parameter such as ?something=<script>alert(1)</script> and observe if the value is reflected unsanitized in the HTML response.
    Affected if The URL parameter value is reflected directly in the HTML response without HTML entity encoding (the <script> tag executes or appears literally in the page source).
  5. Confirm vulnerability in channel-acl.php
    Access the channel-acl.php script directly via browser using a logged-in administrator session. Inject a test parameter such as ?something=<script>alert(1)</script> and observe if the value is reflected unsanitized in the HTML response.
    Affected if The URL parameter value is reflected directly in the HTML response without HTML entity encoding (the <script> tag executes or appears literally in the page source).

You are affected if Revive Adserver version 6.0.4 or lower is installed, the admin interface is accessible, and banner-acl.php or channel-acl.php reflect URL parameters without sanitization.

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 a release after 6.0.4
Interim mitigation

Implement input validation and output encoding for all user-supplied parameters in the affected files. Use context-appropriate encoding (HTML entity encoding) when reflecting any parameter values in the HTML response, and validate that input conforms to expected formats before processing.

Recommended fix Moderate confidence

Revive Adserver 6.0.5 or later stable release

  1. Download the latest stable version of Revive Adserver from the official repository or website
  2. Back up your existing installation and database before upgrading
  3. Extract the new version files and replace the existing installation
  4. Run any available database upgrade scripts if included in the release
  5. Verify the banner-acl.php and channel-acl.php scripts have been updated
  6. Test the application to confirm the XSS vulnerability has been remediated
Caveat Review release notes for any configuration or database changes that may require migration steps

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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