# CVE-2019-15776: Open redirect in n/a

> Attackers can inject malicious 301 redirect rules via CSV files in the simple-301-redirects-addon-bulk-uploader plugin, potentially redirecting users to malicious sites.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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:** 29 Aug 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vvxg-35hg-r5hr

## What is CVE-2019-15776?

CVE-2019-15776 is a medium-severity vulnerability in n/a, published on 29 Aug 2019. 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 simple-301-redirects-addon-bulk-uploader plugin before 1.2.5 for WordPress has no protection against 301 redirect rule injection via a CSV file.

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

## Which versions are affected by CVE-2019-15776?

It affects 1 product.


Products: Webcraftic Simple 301 Redirects-Addon-Bulk Uploader.

## How do I fix CVE-2019-15776?

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

## Is CVE-2019-15776 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-15776 and fix it if it is affected.

What it is: CVE-2019-15776 is a medium-severity vulnerability in n/a, published on 29 Aug 2019. 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-2019-15776 in the wild and no public exploit code.

Affected product: n/a. 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-2019-15776/ (Markdown: https://insights.sbomify.com/CVE-2019-15776/index.md)
```

## Sources

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

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