# CVE-2026-50743: Cross-site request forgery in Adserver

> Attackers can force authenticated administrators to link or unlink banners and campaigns via crafted requests, requiring a patch to prevent unauthorized modifications.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** GHSA-h857-j7g6-gpwf

## What is CVE-2026-50743?

CVE-2026-50743 is a medium-severity vulnerability in Revive Adserver, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A CSRF vulnerability exists in the `zone-include.php` script in Revive Adserver 6.0.7. Linking and unlinking banners or campaigns to zones could be triggered via crafted GET or POST requests without any verification of the CSRF token, allowing an attacker to perform these actions on behalf of an authenticated administrator.

Weakness: CWE-352 (Cross-Site Request Forgery)

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


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

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

## Is CVE-2026-50743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-50743 is a medium-severity vulnerability in Revive Adserver, published on 20 Jul 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-50743 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-50743/ (Markdown: https://insights.sbomify.com/CVE-2026-50743/index.md)
```

## Sources

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

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