CVE-2026-44957
Deferred Deferred - Pending Action
Missing Access Control in Revive Adserver XML-RPC API

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: HackerOne

Description
A missing access control check when invoking various modify methods in the XML‑RPC API of Revive Adserver 6.0.6 and earlier. The API allowed entities to be reassigned to different parent entities, leading to inconsistent ownership relationships. This issue was exploitable only in combination with CVE‑2026‑34917 or with third‑party API extensions that expose API functionality to low‑privileged users. Access control checks have been added to validate access to parent entities in the API modify methods.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-23
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
CVE-2026-44957
EUVD
EUVD-2026-38502
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
revive_adserver revive_adserver to 6.0.6 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-284 The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is due to a missing access control check in the XML-RPC API of Revive Adserver version 6.0.6 and earlier. Specifically, when invoking various modify methods, the API allowed entities to be reassigned to different parent entities without proper validation. This could lead to inconsistent ownership relationships within the system.

The issue can only be exploited if combined with another vulnerability (CVE-2026-34917) or through third-party API extensions that expose API functionality to users with low privileges. The fix involved adding access control checks to validate access to parent entities when using the API's modify methods.

Impact Analysis

This vulnerability can impact you by allowing unauthorized reassignment of entities to different parent entities within Revive Adserver, potentially causing inconsistent ownership relationships.

Such unauthorized modifications could lead to integrity issues in the system's data and may allow low-privileged users to perform actions they should not be permitted to do, especially if combined with other vulnerabilities or insecure third-party extensions.

According to the CVSS score (4.3), the impact is limited to integrity with no direct impact on confidentiality or availability.

Mitigation Strategies

To mitigate this vulnerability, ensure that you upgrade Revive Adserver to a version later than 6.0.6 where access control checks have been added to the XML-RPC API modify methods.

Additionally, restrict access to the XML-RPC API to trusted and privileged users only, and avoid using third-party API extensions that expose API functionality to low-privileged users.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44957. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart