VYPR

Really Simple Security

by WordPress

CVEs (6)

  • CVE-2024-10924CriNov 15, 2024
    risk 0.66cvss 9.8epss 0.82

    The Really Simple Security (Free, Pro, and Pro Multisite) plugins for WordPress are vulnerable to authentication bypass in versions 9.0.0 to 9.1.1.1. This is due to improper user check error handling in the two-factor REST API actions with the 'check_login_and_get_user'…

  • CVE-2026-89080HigSep 13, 2026
    risk 0.49cvss 7.5epss 0.00

    The Really Simple Security WordPress plugin before 9.8.1 does not prevent an unauthenticated request from resetting an account's completed email two-factor enrolment, allowing an attacker who already knows the account's password to bypass the second factor and obtain that…

  • CVE-2026-8293HigJun 2, 2026
    risk 0.49cvss 7.5epss 0.00

    The Really Simple Security WordPress plugin before 9.5.10.1 does not enforce the second-factor challenge in two of its two-factor authentication REST endpoints, allowing an attacker who knows a user's password to obtain a WordPress authentication session for that user without…

  • CVE-2026-81766MedAug 30, 2026
    risk 0.43cvss 6.6epss 0.00

    The Really Simple Security WordPress plugin before 9.8.0 does not check that the user is allowed to install Really Simple Security WordPress plugin before 9.8.0 before installing one from a user-supplied URL, allowing an administrator of a subsite on a multisite network to…

  • CVE-2026-88798MedSep 18, 2026
    risk 0.34cvss 5.3epss 0.00

    The Really Simple Security WordPress plugin before 9.8.3 does not validate a client-supplied address value before using it as a storage key in one of its own options, allowing unauthenticated attackers to grow that option without bound and to slow the site's handling of missing…

  • CVE-2026-82519MedSep 14, 2026
    risk 0.28cvss 4.3epss 0.00

    Really Simple Security plugin for WordPress before 9.8.2 contains a missing authorization check vulnerability that allows authenticated low-privileged attackers to bypass enforced two-factor authentication indefinitely by exploiting an unguarded code path in the profile-page…