dbcve.org
Improper AuthenticationWeakness · CWE-287

CVE-2026-8293

HIGH · 7.5 CVSS v3.1 Published 2026-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 completing the email OTP challenge.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Really Simple Security WordPress plugin versions prior to 9.5.10.1 fail to enforce the email OTP second-factor challenge on two REST endpoints used in the two-factor authentication flow. An attacker who has compromised a user's password can bypass the 2FA requirement entirely and obtain a valid WordPress authentication session without completing the email OTP verification.

MitigationUpdate Really Simple Security plugin to version 9.5.10.1 or later, which enforces the 2FA challenge on both vulnerable REST endpoints. Alternatively, disable the plugin's 2FA feature until the update can be applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Really Simple Security plugin is installed
    Navigate to WordPress admin > Plugins or run 'wp plugin list' via WP-CLI to list installed plugins
    Affected if The plugin is not installed or has been removed entirely, then the vulnerability does not apply
  2. Determine the installed version of Really Simple Security
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number next to Really Simple Security, or run 'wp plugin get really-simple-security --format=version' via WP-CLI
    Affected if The installed version is earlier than 9.5.10.1 (e.g., 9.5.10, 9.5.9, 9.5.0, etc.)
  3. Verify if 2FA with email OTP is enabled
    Go to Really Simple Security settings in WordPress admin and check if two-factor authentication is activated, specifically looking for email-based OTP (one-time password) as an enabled 2FA method
    Affected if 2FA is disabled entirely or email OTP is not configured as an authentication method, then the bypass cannot be exploited
  4. Confirm the vulnerable REST endpoints are accessible
    Attempt a GET request to the plugin's 2FA REST endpoints (commonly at /wp-json/rsssl/v1/2fa/ or similar paths under the rsssl namespace) using a tool like curl or a browser to verify they respond
    Affected if The REST endpoints return a valid JSON response rather than a 404 or 403 error, indicating the 2FA REST functionality is active and potentially exploitable

A user is affected if the Really Simple Security plugin is installed with a version before 9.5.10.1 AND email OTP-based 2FA is enabled and the REST endpoints are accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Really Simple Security plugin to version 9.5.10.1 or later, which enforces the 2FA challenge on both vulnerable REST endpoints. Alternatively, disable the plugin's 2FA feature until the update can be applied.

Recommended fix Moderate confidence

Really Simple Security version 9.5.10.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Really Simple Security' in the plugin list
  4. Click 'Update now' if an update is available, or manually download version 9.5.10.1 or later from wordpress.org and upload via Plugins > Add New > Upload Plugin
  5. Verify the plugin version is 9.5.10.1 or higher after updating
  6. Test that two-factor authentication REST endpoints now properly enforce the email OTP challenge

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8293 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8293 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data