CVE-2026-8903 MEDIUM

CVE-2026-8903: Two-factor authentication (formerly IP Vault) <= 2.1 - Cross-Site Request Forgery to Settings Update

Vendor Youtag
Product Two-factor authentication (formerly IP Vault)
Weakness CWE-352 · CSRF
Published May 27, 2026
Last update May 27, 2026

CVSS base score

4.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality None
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

What the vulnerability does

01Description

The Two-factor authentication (formerly IP Vault) plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.1. This is due to missing or incorrect nonce validation on the ipv_save_changes function. This makes it possible for unauthenticated attackers to modify the plugin's firewall and two-factor authentication settings — including the operating mode, request include/exclude rules, authentication slug, and log retention period — potentially disabling protection entirely via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

Explanation of Vulnerability in Simple Terms

02Summary

The Two-Factor Authentication plugin for youtag contains a cross-site request forgery (CSRF) vulnerability in versions 2.1 and earlier. An attacker can craft a malicious webpage that, when visited by a logged-in site administrator, performs unwanted actions on the site without their knowledge. The vulnerability requires user interaction but does not require authentication to set up the attack.

What an attacker can do

03Attacker Capabilities

Trick a logged-in admin into performing unwanted actions on the site via a malicious webpage.

Potential impact on your site

04Site Impact

Admins could unknowingly change settings or perform actions if tricked into visiting a malicious link.

Conditions required to exploit

05Prerequisites

Admin must visit attacker-controlled webpage while logged into the site.

Key dates

06Disclosure timeline

May 27, 2026 CVE published
May 27, 2026 Record updated

Related vulnerabilities

08Related CVE