dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-58979

MEDIUM · 5.3 CVSS v3.1 Published 2025-09-09
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 BerqWP BerqWP searchpro allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects BerqWP: from n/a through <= 2.2.53.

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

Missing authorization vulnerability in BerqWP plugin's searchpro feature allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to restricted functionality.

MitigationUpdate BerqWP to the latest version beyond 2.2.53 which should contain a patch, or implement proper authorization checks on all searchpro endpoints and administrative functions.

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 BerqWP plugin is installed
    Check WordPress plugin directory for berqwp folder, or in WP-Admin go to Plugins > Installed Plugins and look for BerqWP, or run: wp plugin list --name=berqwp
    Affected if BerqWP plugin is not found on the system
  2. Determine installed BerqWP version
    In WP-Admin, go to Plugins > Installed Plugins > BerqWP and note the version number displayed, or run: wp plugin get berqwp --format=version
    Affected if Version is present and below 2.2.53
  3. Verify searchpro feature is active
    Check if the searchpro functionality is enabled in plugin settings under BerqWP configuration, or attempt to access a searchpro endpoint such as /?s=test&searchpro=1 and observe if the feature responds
    Affected if searchpro feature is enabled and responding to requests
  4. Test unauthorized access to searchpro endpoint
    Make an unauthenticated HTTP request to the searchpro endpoint (e.g., /?s=anything&searchpro=1) and verify whether restricted data or functionality is returned without login
    Affected if searchpro endpoint returns restricted content to unauthenticated users

Environment is affected if BerqWP plugin version is below 2.2.53 and the searchpro feature is enabled, allowing unauthenticated access to restricted functionality

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update BerqWP to the latest version beyond 2.2.53 which should contain a patch, or implement proper authorization checks on all searchpro endpoints and administrative functions.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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