# CVE-2026-44958: Missing authorization in Adserver

> Advertisers can bypass permissions to activate or deactivate banners in Revive Adserver, allowing unauthorized modification of ad status.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Jun 2026
- **Updated:** 23 Jun 2026
- **Also known as:** GHSA-hqvw-xvc4-mxq4

## What is CVE-2026-44958?

CVE-2026-44958 is a medium-severity missing authorization vulnerability in Revive Adserver, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An access control bypass allows an advertiser‑level user 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. The status field has been removed from the hidden form fields in the banner edit screen.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2026-44958?


## How do I fix CVE-2026-44958?

No fix has been published for CVE-2026-44958 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-44958 being exploited?

There is no known exploitation of CVE-2026-44958 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44958 and fix it if it is affected.

What it is: CVE-2026-44958 is a medium-severity missing authorization vulnerability in Revive Adserver, published on 23 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-44958 in the wild and no public exploit code.

Affected product: Revive Adserver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44958/ (Markdown: https://insights.sbomify.com/CVE-2026-44958/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44958
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44958
- OSV: https://osv.dev/vulnerability/CVE-2026-44958

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44958/
Summaries are generated and may contain mistakes; the official description above is the record.