# CVE-2019-11016: Elgg open redirect

> An open redirect vulnerability in Elgg allows attackers to redirect users to malicious sites, potentially facilitating phishing attacks.

- **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:** Yes
- **Published:** 8 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-r6h7-846c-8m78

## What is CVE-2019-11016?

CVE-2019-11016 is a medium-severity vulnerability in n/a, published on 8 Apr 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

Elgg before 1.12.18 and 2.3.x before 2.3.11 has an open redirect.

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

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

4 open source packages ship an affected version, including elgg/elgg. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `elgg/elgg` | Packagist | All versions | 1.12.18 |
| `elgg/elgg` | Packagist | All versions | 1.12.18 |
| `elgg/elgg` | Packagist | From 2.3.0 | 2.3.11 |
| `elgg/elgg` | Packagist | From 2.3.0 | 2.3.11 |

Products: Elgg Elgg.

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

Upgrade elgg/elgg to a fixed version for your release line: 1.12.18 or 2.3.11.

## Is CVE-2019-11016 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-2936](https://insights.sbomify.com/CVE-2011-2936/): SQL injection in Elgg (critical 9.8)
- [CVE-2021-4072](https://insights.sbomify.com/CVE-2021-4072/): Cross-site Scripting (XSS) - Stored in elgg/elgg (critical 9.0)
- [CVE-2012-6562](https://insights.sbomify.com/CVE-2012-6562/): Missing authorization in n/a (medium 6.8)
- [CVE-2011-2935](https://insights.sbomify.com/CVE-2011-2935/): Elgg Reflected XSS Vulnerability (medium 6.1)
- [CVE-2021-3980](https://insights.sbomify.com/CVE-2021-3980/): Exposure of Private Personal Information to an Unauthorized Actor in elgg/elgg (medium 5.3)

## Fix prompt for AI coding agents

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

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

Affected packages and fixed versions:
- elgg/elgg (Packagist): affected all versions; fixed in 1.12.18
- elgg/elgg (Packagist): affected all versions; fixed in 1.12.18
- elgg/elgg (Packagist): affected from 2.3.0; fixed in 2.3.11
- elgg/elgg (Packagist): affected from 2.3.0; fixed in 2.3.11

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-11016/ (Markdown: https://insights.sbomify.com/CVE-2019-11016/index.md)
```

## Sources

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

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