CVE-2016-15030: A vulnerability classified as problematic has been found in Arno0x TwoFactorAuth

Q: How do I fix CVE-2016-15030?

twofactorauth: upgrade to 2016-01-27. Exact commands for each OS are on this page.

Q: Is CVE-2016-15030 being exploited?

CVE-2016-15030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-15030 affect?

CVE-2016-15030 affects twofactorauth. Severity is low (CVSS 3.5). 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

Q: How urgent is CVE-2016-15030?

Priority 22/100. No elevated risk signals yet.

Routine

LOW 3.5UPGRADE

CVE-2016-15030 is a low-severity flaw (CVSS 3.5) affecting twofactorauth. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	3.5 (Low)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	Required
EPSS exploit chance	0.4% (top 63%)
CISA exploited list	No
Weakness	CWE-601
Published	2023-03-25
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: twofactorauth project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2023-03-25 18:15 UTCPublished CVE record published
2026-06-17 00:41 UTCUpdated Record last modified

twofactorauth project twofactorauth UPGRADE

Affected: < 2016-01-27

Fixed in: 2016-01-27

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy twofactorauth || rpm -q twofactorauth || twofactorauth --version

2. UPGRADE to 2016-01-27 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade twofactorauth

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade twofactorauth

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-15030?

twofactorauth: upgrade to 2016-01-27. Exact commands for each OS are on this page.

Is CVE-2016-15030 being exploited?

CVE-2016-15030 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-15030 affect?

CVE-2016-15030 affects twofactorauth. Severity is low (CVSS 3.5). 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

How urgent is CVE-2016-15030?

Priority 22/100. No elevated risk signals yet.

Software pages

PHP vulnerabilities

References

← Back to latest CVEs