<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-11-14T19:30:45.039078+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/fkie_cve-2026-82978</id>
    <title>fkie_cve-2026-82978</title>
    <updated>2026-11-14T19:30:45.040888+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An authorization bypass in channel-edit.php in Revive Adserver 6.0.8 and earlier allows an authenticated manager to create a delivery rule set belonging to another agency by changing the submitted agencyid parameter. The server trusts the submitted agency identifier when inserting the new rule set, allowing unauthorized creation of objects in another agency's account. The issue is fixed in Revive Adserver 6.0.9 by obtaining the agency identifier from the authenticated account rather than submitted form data and removing the agency identifier from the form's hidden fields.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/fkie_cve-2026-82978"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/gcve-1988-2026-0565</id>
    <title>GCVE-1988-2026-0565 — [REVIVE-SA-2026-004] Revive Adserver Vulnerabilities</title>
    <updated>2026-11-14T19:30:45.040969+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> unknown Revive Adserver Vulnerabilities</p>
<p>========================================================================
Revive Adserver Security Advisory                     REVIVE-SA-2026-004
------------------------------------------------------------------------
https://www.revive-adserver.com/security/revive-sa-2026-004
------------------------------------------------------------------------
Date:                  2026-11-11
Risk Level:            Medium to High
Applications affected: Revive Adserver
Versions affected:     &lt;= 6.0.8
Versions not affected: &gt;= 6.0.9
Website:               https://www.revive-adserver.com/
========================================================================</p>
<p>========================================================================
1. Blind SQL injection through inconsistent request precedence
========================================================================
Vulnerability Type:    CWE-89: SQL Injection
CVE-ID:                CVE-2026-107662
Risk level:            High
CVSS Base Score:       8.8
CVSS Vector:           CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
------------------------------------------------------------------------</p>
<p>Description
-----------</p>
<p>Resolution
----------</p>
<p>References
----------
https://hackerone.com/reports/3896779
https://github.com/revive-adserver/revive-adserver/commit/e301dbbb7
https://github.com/revive-adserver/revive-adserver/commit/0aa9d0124
https://cwe.mitre.org/data/definitions/89.html</p>
<p>========================================================…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/gcve-1988-2026-0565"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/ghsa-5p98-2ff8-345c</id>
    <title>GHSA-5p98-2ff8-345c</title>
    <updated>2026-11-14T19:30:45.041059+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>An authorization bypass in channel-edit.php in Revive Adserver 6.0.8 and earlier allows an authenticated manager to create a delivery rule set belonging to another agency by changing the submitted agencyid parameter. The server trusts the submitted agency identifier when inserting the new rule set, allowing unauthorized creation of objects in another agency's account. The issue is fixed in Revive Adserver 6.0.9 by obtaining the agency identifier from the authenticated account rather than submitted form data and removing the agency identifier from the form's hidden fields.</p>
      </div>
    </content>
    <link href="https://db.gcve.eu/vuln/ghsa-5p98-2ff8-345c"/>
  </entry>
</feed>
