CVE-2026-107247 · Package
NO FIX YET · SEE WHAT TO DO
Revive Adserver 6.0.0 through 6.0.8 gives GET parameters precedence over POST parameters in its admin forms, so an authenticated manager limited to one agency can send one object ID in the query string and another in the form body. The permission check and the change then hit different objects, letting the manager modify other agencies' campaigns and read campaign and banner data.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Any Revive Adserver instance on 6.0.0 through 6.0.8 where more than one agency or manager account shares the admin interface. Single-agency installs with only trusted administrators face little added risk from cross-agency access. Instances on 6.0.9 or later are not affected.
Not affected if single-agency-install, version-6.0.9-or-later
Who cares ad-tech, revive-adserver, self-hosted
6.0.0 through 6.0.8 are affected)156dee7bc3283c128f35e5a31bb305054cc8de1b in the deployed code if you build from source6.0.9, which restores POST precedence in global input registrationAn authorization bypass in Revive Adserver 6.0.0 through 6.0.8 allows an authenticated manager restricted to one agency to access or modify resources belonging to another agency. Global input registration gives GET parameters precedence over POST parameters, while submitted administration forms use POST values. By supplying authorized object identifiers in the query string and different identifiers in the POST body, an attacker can cause permission checks and subsequent operations to target different objects. This permits unauthorized cross-agency changes, campaign ownership reassignment and disclosure of campaign and banner data. The regression was introduced in commit 156dee7bc3283c128f35e5a31bb305054cc8de1b and is fixed in Revive Adserver 6.0.9 by restoring POST precedence in global input registration.
This page as .md · .json · CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.