dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-58667

MEDIUM · 5.4 CVSS v3.1 Published 2025-09-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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
Missing Authorization vulnerability in CridioStudio ListingPro Reviews listingpro-reviews allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects ListingPro Reviews: from n/a through < 2.9.11.

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 the ListingPro Reviews WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to review-related functionality or data that should require elevated privileges.

MitigationUpdate ListingPro Reviews plugin to version 2.9.11 or later to obtain the patched authorization controls.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Confirm ListingPro Reviews plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'ListingPro Reviews' in the list
    Affected if The plugin appears in the installed plugins list and is activated
  2. Check installed plugin version
    In WordPress admin, go to Plugins > Installed Plugins, find ListingPro Reviews, and note the version number displayed beneath the plugin name
    Affected if The version number is lower than 2.9.11 (versions prior to 2.9.11 contain the missing authorization vulnerability)
  3. Inspect access control configuration
    Review plugin settings under Listings > Reviews or a similar admin menu item for authorization or access control options; verify that review-related endpoints require proper authentication
    Affected if The plugin allows unauthenticated or low-privilege users to access review data or administrative review functions that should require elevated permissions
  4. Review access logs for unauthorized review access
    Check WordPress debug logs, server access logs, or security plugins for requests to review-related AJAX endpoints or API routes originating from unauthenticated users
    Affected if Unauthenticated users successfully accessed review creation, modification, deletion, or export functionality that should be restricted to logged-in administrators or editors

A user is affected if the ListingPro Reviews plugin is installed with a version lower than 2.9.11 and the missing authorization allows unauthenticated or low-privilege access to review-related 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.

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

Update ListingPro Reviews plugin to version 2.9.11 or later to obtain the patched authorization controls.

Recommended fix Moderate confidence

2.9.11

  1. Backup your WordPress site and database before making any changes
  2. Update the ListingPro Reviews plugin to version 2.9.11 or later through the WordPress admin dashboard (Plugins > All Plugins > ListingPro Reviews > Update Now)
  3. Verify the update was successful by checking the plugin version number
  4. Test critical functionality related to reviews and listings to ensure the update did not break existing features
  5. Confirm that the authorization controls are now properly enforced

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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