dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-27357

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/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
Missing Authorization vulnerability in Cornel Raiu WP Search Analytics allows Exploiting Incorrectly Configured Access Control Security Levels. This issue affects WP Search Analytics: from n/a before 1.5.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

The WP Search Analytics plugin before version 1.5.0 contains a missing authorization vulnerability that allows attackers to exploit incorrectly configured access control security levels. This is a broken access control issue where the plugin fails to properly verify user permissions before allowing access to certain functionality or data.

MitigationUpgrade WP Search Analytics to version 1.5.0 or later to obtain the patched version with proper authorization controls implemented.

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
None

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

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. Confirm WP Search Analytics is installed
    Navigate to WordPress admin dashboard > Plugins and look for 'WP Search Analytics' in the installed plugins list, or check the wp-content/plugins directory for a folder named 'wp-search-analytics' or similar
    Affected if Plugin is installed and active on the WordPress site
  2. Identify the installed plugin version
    In WordPress admin > Plugins > Installed Plugins, find WP Search Analytics and note the version number displayed under the plugin name. Alternatively, check the main plugin PHP file header for the 'Version' tag
    Affected if Version is present and is lower than 1.5.0, or if no version number can be determined (indicating an older release)
  3. Test for unauthorized access to plugin functions
    Log in as a subscriber or contributor-level user (a low-privilege user) and attempt to access the WP Search Analytics admin pages directly via URL (e.g., /wp-admin/admin.php?page=wp-search-analytics), or check if plugin endpoints respond to authenticated requests from non-admin users
    Affected if Low-privilege authenticated users can access plugin admin pages, view search analytics data, or execute plugin functions without receiving a permission denied error
  4. Inspect user role capabilities for plugin access
    Review WordPress user roles and capabilities, or use a role management plugin to check whether subscriber/contributor/editor roles have been granted capabilities related to the plugin (such as 'manage_options' or custom capabilities added by the plugin)
    Affected if Non-administrator roles have elevated capabilities that should not be granted, allowing them to access plugin functionality

A user is affected if the WP Search Analytics plugin is installed with a version prior to 1.5.0 AND low-privilege authenticated users can access plugin admin pages or data without proper authorization checks.

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

Upgrade WP Search Analytics to version 1.5.0 or later to obtain the patched version with proper authorization controls implemented.

Recommended fix Moderate confidence

1.5.0

  1. Back up your WordPress site database and files before making any changes
  2. Navigate to WordPress admin dashboard > Plugins > Installed Plugins
  3. Locate WP Search Analytics plugin
  4. Click 'Update now' if an update is available, or manually upload version 1.5.0 or later from the WordPress plugin repository
  5. Verify the plugin version is 1.5.0 or higher after updating
  6. Test that the WP Search Analytics functionality works correctly post-update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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