Skip to main content
CVE-2026-77168VulnerabilityPublished

tracker-invocation.php · Cross-site Request Forgery Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-77168· Medium 4.3

Not known to be exploited · CVSS 4.3 Medium · fixed in 6.0.9 : update Adserver when convenient.

Data as of 11 Nov 2026, 19:38 UTC

CVSS 3.0 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (hackerone)CVSS 3.04.3
Patch
Available – fixed in 6.0.9
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
ReviveAdserverAffected
  • <=6.0.8
Fixed in–
Packagistrevive/adserverpkg:composer/revive/adserverOther threatsAffected
  • <=6.0.8
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to Revive Adserver version 6.0.9 or later, which removes the vulnerable tracker-modification handler. No other mitigation is indicated as the fix eliminates the attack vector.

Description

A cross-site request forgery (CSRF) vulnerability exists in tracker-invocation.php in Revive Adserver version 6.0.8 and earlier. This flaw allows an attacker to modify a tracker's name, description, or advertiser assignment by leveraging an authenticated victim's permissions. The vulnerability arises from a leftover state-changing handler that processes request parameters without verifying a CSRF token. Exploitation requires victim interaction and the victim's session credentials to be included in the request. The issue is addressed in Revive Adserver 6.0.9 by removing the unused tracker-modification handler.

References

Community reviews

Loading reviews…