# CVE-2016-15030: Arno0x TwoFactorAuth login.php redirect

> Attackers can redirect users to malicious sites via the login page, potentially facilitating phishing attacks against TwoFactorAuth users.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Mar 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w3m5-m73f-fm2c

## What is CVE-2016-15030?

CVE-2016-15030 is a low-severity vulnerability in Arno0x TwoFactorAuth, published on 25 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability classified as problematic has been found in Arno0x TwoFactorAuth. This affects an unknown part of the file login/login.php. The manipulation of the argument from leads to open redirect. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named 8549ad3cf197095f783643e41333586d6a4d0e54. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-223803.

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

## Which versions are affected by CVE-2016-15030?

It affects 1 product.


Products: Twofactorauth Project Twofactorauth.

## How do I fix CVE-2016-15030?

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

## Is CVE-2016-15030 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-15030 and fix it if it is affected.

What it is: CVE-2016-15030 is a low-severity vulnerability in Arno0x TwoFactorAuth, published on 25 Mar 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-15030 in the wild and no public exploit code.

Affected product: Arno0x TwoFactorAuth. 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-2016-15030/ (Markdown: https://insights.sbomify.com/CVE-2016-15030/index.md)
```

## Sources

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

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