CVE.org (no NVD analysis yet)· CNA drupal

CVE-2026-107268: Two Factor Authentication - TFA / Passwordless Login - Moderately critical - Information disclosure - SA-CONTRIB-2026-207

MediumCVSS 4.3 · v3.1—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 17/100)

Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
Probability of exploitation in the next 30 days: 0.29% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: Drupal Two Factor Authentication - TFA / Passwordless Login 5.4.1, 5.5.2.
Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to Drupal Two Factor Authentication - TFA / Passwordless Login 5.4.1, 5.5.2 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Insertion of Sensitive Information Into Sent Data vulnerability in Drupal Two Factor Authentication - TFA / Passwordless Login allows Forceful Browsing. This issue affects Two Factor Authentication - TFA / Passwordless Login versions: from 0.0.0 to 5.4.1, from 5.5.0 to 5.5.2.

Published: Oct 30, 2026
Updated: Oct 30, 2026
EPSS: 0.2% · 22th percentile
CWE: CWE-201

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 17 / 40 · 4.3 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
Proof of concept exists, no weaponized module
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (drupal). Independent of NVD's CPE analysis and usually ahead of it.

Drupal Two Factor Authentication - TFA / Passwordless Login
- 0.0.0 and later · before 5.4.1affected · semver
- 5.5.0 and later · before 5.5.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Ecosystem	Package	Affected range	Fix
Packagist:https://packages.drupal.org/8	drupal/miniorange_2fa	from 5.5.0 · before 5.5.2	5.5.2
Packagist:https://packages.drupal.org/8	drupal/miniorange_2fa	before 5.4.1	5.4.1

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
Drupal Two Factor Authentication - TFA / Passwordless Login	5.4.1	Vendor (CNA)
Drupal Two Factor Authentication - TFA / Passwordless Login	5.5.2	Vendor (CNA)
Packagist:https://packages.drupal.org/8:drupal/miniorange_2fa	5.4.1	Package registry (OSV)
Packagist:https://packages.drupal.org/8:drupal/miniorange_2fa	5.5.2	Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
Source	Kind	Date
Proof-of-concept repository on GitHub	stars:0	2026-10-08

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.