dbcve.org
Revive AdserverApplication · Aquaplatform

CVE-2026-21664

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 Huynh Pham Thanh Luc (nigh7c0r3) has reported a reflected XSS vulnerability in the afr.php delivery script 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

Reflected XSS in Revive Adserver's afr.php delivery script allows an attacker to inject malicious HTML/JavaScript via a URL parameter. When a logged-in administrator clicks a crafted link, the payload reflects back and executes in their browser context.

MitigationFix requires implementing proper input validation and output encoding on the affected parameter in afr.php to prevent untrusted input from being rendered as executable HTML/JavaScript.

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.0, <= 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 version
    Locate the version file or header in the Revive Adserver installation - typically in a VERSION file or within the main configuration. Common paths include the root directory or a lib/ subdirectory. Read the version number.
    Affected if The installed version is 6.0.0, 6.0.1, 6.0.2, 6.0.3, or 6.0.4 (any version from 6.0.0 through 6.0.4 inclusive)
  2. Confirm afr.php delivery script is present
    Search for the afr.php file in the web-accessible directories of the Revive Adserver installation, typically under the www/delivery/ or similar delivery script directory.
    Affected if The afr.php file exists in the installation and is accessible via web requests
  3. Check if the application has administrator accounts configured
    Review the Revive Adserver database or configuration to determine if administrator accounts exist and whether admin access is enabled.
    Affected if There are active administrator accounts configured in the system, as the attack requires a logged-in administrator to trigger the XSS

The environment is affected if the installed Aquaplatform Revive Adserver version is between 6.0.0 and 6.0.4 inclusive, the afr.php delivery script is present, and administrator accounts are configured and accessible.

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

Fix requires implementing proper input validation and output encoding on the affected parameter in afr.php to prevent untrusted input from being rendered as executable HTML/JavaScript.

Recommended fix Moderate confidence

Latest stable Revive Adserver release (beyond 6.0.4, e.g., 6.1.0 or later)

  1. 1. Back up the current Revive Adserver installation, including database and configuration files
  2. 2. Download the latest stable version of Revive Adserver from the official repository (https://www.revive-adserver.com/)
  3. 3. Follow the standard upgrade documentation for Revive Adserver
  4. 4. Replace the existing afr.php delivery script with the updated version from the download
  5. 5. Clear any application caches if enabled
  6. 6. Verify the fix by testing that the afr.php script properly sanitizes parameters
Caveat Review release notes for any configuration or database migration requirements between 6.0.x and newer versions

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