Revive Adserver vulnerabilities

A missing validation of user input exists when saving delivery limitations in Revive Adserver 6.0.6 and earlier. A low-privileged user could add an unexpected component parameter and inject malicious PHP code into the compiledlimitations field, which would then be executed during banner delivery.

The vulnerability allows advertiser-level users to activate or deactivate a banner in Revive Adserver 6.0.6 and earlier, even when such permissions were not granted. The banner-edit.php script allowed the banner status to be overwritten solely based on banner edit permissions.

A missing validation of user input when saving delivery limitations in Revive Adserver 6.0.6 and earlier could allow a low-privileged user to inject malicious PHP code into the compiledlimitations field on the database, resulting in its execution during banner delivery.

Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). The Revive Adserver team conducted a security audit of the admin interface scripts to identify and fix other potential CSRF vulnerabilities.

Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF). Several scripts in Revive Adserver's user interface are vulnerable to these attacks.

Revive Adserver before 3.2.3 suffers from Cross-Site Request Forgery (CSRF) in the password recovery form. This vulnerability could be exploited to send a large number of password recovery emails to registered users.

Directory traversal vulnerability in delivery-dev/al.php in Revive Adserver before 3.2.2 allows remote attackers to include and execute arbitrary local files via a .. (dot dot) in the layerstyle parameter.

The default Flash cross-domain policy (crossdomain.xml) in Revive Adserver before version 3.2.2 does not restrict access from other domains, allowing remote attackers to conduct cross-domain attacks via unspecified vectors.

Revive Adserver before 3.2.2 allows remote attackers to perform unspecified actions by leveraging an unexpired session after the user has been deleted or unlinked.

Revive Adserver versions before 3.2.5 and 4.0.0 are vulnerable to Reflected File Download (RFD) attacks. Attackers can exploit the vulnerability in `www/delivery/asyncspc.php` to remotely download a file onto the victim's machine.

Revive Adserver before 3.2.3 suffers from session fixation, allowing arbitrary session identifiers to be forced. Additionally, it does not invalidate the existing session upon successful authentication, which could enable an attacker to steal an authenticated session.

Revive Adserver before version 3.2.3 suffers from improper restriction of excessive authentication attempts. The login page is vulnerable to password-guessing attacks, which may lead to unauthorized access.

Revive Adserver before 4.0.1 allows remote attackers to execute arbitrary code via serialized data in the cookies related to the delivery scripts.

Revive Adserver 6.0.7 contains a CSRF vulnerability in the `zone-include.php` script. Linking and unlinking banners or campaigns to zones can be triggered via crafted GET or POST requests without CSRF token verification, allowing an attacker to perform these actions on behalf of an authenticated administrator.

A bypass to the admin-only restriction of the XML-RPC API in Revive Adserver 6.0.7. The API response for the ox.login method returned a session ID cookie in the HTTP headers, and although the method correctly returned an error, the associated session was not invalidated, allowing the leaked session ID to be used for subsequent unrestricted API calls.

A stored XSS vulnerability exists in the maintenance-acl-check.php and maintenance-banners-check.php tools of Revive Adserver 6.0.7. Entity names are displayed without proper escaping when inconsistencies are detected.

In Revive Adserver 6.0.7 and earlier, missing sanitization of user input in the zone-include.php script allows XSS attacks. A low-privileged user can exploit the refresh parameter of the iFrame invocation tag to perform reflected XSS attacks.

A bypass for CVE-2026-34913 exists in Revive Adserver 6.0.7 and earlier due to missing ownership validation in the reverse operation of linking campaigns and trackers via the `tracker-campaigns.php` script. A low-privileged user can link their trackers to campaigns owned by other managers on the same instance, causing inconsistent ownership relationships.