# CVE-2026-88791: Safe Redirect Manager < 2.3.0 - Open Redirect via Wildcard Redirect Rules

> Unauthenticated attackers can redirect users to arbitrary external sites via crafted requests when wildcard redirect rules are configured in Safe Redirect Manager.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:N/I:L/A:N`)
- **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:** 30 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-xxpw-g4gr-qqvv

## What is CVE-2026-88791?

CVE-2026-88791 is a low-severity vulnerability in Unknown Safe Redirect Manager, published on 30 Sep 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

The Safe Redirect Manager WordPress plugin before 2.3.0 does not properly validate the redirect destination when a wildcard redirect rule to an absolute URL is configured, allowing unauthenticated attackers to redirect visitors to an arbitrary external website via a crafted request path.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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


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

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

## Is CVE-2026-88791 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88791 is a low-severity vulnerability in Unknown Safe Redirect Manager, published on 30 Sep 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-88791 in the wild and no public exploit code.

Affected product: Unknown Safe Redirect Manager. 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-88791/ (Markdown: https://insights.sbomify.com/CVE-2026-88791/index.md)
```

## Sources

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

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