Two-factor authentication (formerly IP Vault) <= 2.1 - Cross-Site Request Forgery to Settings Update
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| youtag | Two-factor authentication (formerly IP Vault) | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Wordpress | Wordpress |
|
||||||||
| Youtag | Two-factor Authentication (formerly Ip Vault) |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.139% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Wordpress
Wordpress wordpress Youtag Youtag two-factor Authentication (formerly Ip Vault) |
|
| Vendors & Products |
Wordpress
Wordpress wordpress Youtag Youtag two-factor Authentication (formerly Ip Vault) |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Two-factor authentication (formerly IP Vault) <= 2.1 - Cross-Site Request Forgery to Settings Update | |
| Weaknesses | CWE-352 | |
| References |
|
|
| Metrics |
cvssV3_1
|