dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-27397

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Authorization Bypass Through User-Controlled Key vulnerability in Really Simple Plugins B.V. Really Simple Security Pro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Really Simple Security Pro: from n/a through 9.5.4.0.

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 · moderate confidence

Authorization bypass vulnerability in Really Simple Security Pro WordPress plugin where user-controlled key input allows exploiting incorrectly configured access control security levels, potentially enabling unauthorized access to security functionality.

MitigationUpdate Really Simple Security Pro beyond version 9.5.4.0 to obtain vendor patch for proper access control validation on user-supplied keys.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

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

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. Locate the Really Simple Security Pro plugin
    Check the WordPress plugins directory or access the plugin management interface in wp-admin to verify Really Simple Security Pro is installed
    Affected if Plugin is installed and active in WordPress
  2. Identify the installed plugin version
    Access the Plugins page in WordPress admin, locate Really Simple Security Pro, and view the version number displayed beneath the plugin name
    Affected if Version is 9.5.4.0 or lower (any version up to and including 9.5.4.0)
  3. Verify security functionality access control configuration
    Navigate to the plugin settings in WordPress admin under Really Simple Security settings. Check the access control or security levels configuration where user-controlled keys may define permissions
    Affected if Access control settings allow user-supplied key input to define security levels without proper validation
  4. Inspect for misconfigured security level assignments
    Review the plugin database options table (wp_options) for entries related to security levels, access control keys, or permission settings that accept user-provided values
    Affected if Configuration entries show user-controlled keys being used to assign or modify security access levels

The environment is affected if Really Simple Security Pro version 9.5.4.0 or lower is installed and the plugin has access control configurations that accept user-supplied keys for security level assignments.

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 Pro beyond version 9.5.4.0 to obtain vendor patch for proper access control validation on user-supplied keys.

Recommended fix Moderate confidence

Upgrade to the latest available version of Really Simple Security Pro (check WordPress plugin repository or your license for current version beyond 9.5.4.0)

  1. 1. Backup your WordPress site and database before making any changes.
  2. 2. Navigate to Plugins > Installed Plugins in your WordPress admin dashboard.
  3. 3. Locate 'Really Simple Security Pro' (also known as Really Simple Security).
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. Verify the update completed successfully by checking the plugin version after updating.
  6. 6. Test that the security plugin functionality is working correctly after the update.
  7. 7. If automatic updates are not enabled, consider enabling them for this plugin or manually check for updates regularly.

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27397 — 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-27397 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