dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-69190

HIGH · 7.3 CVSS v3.1 Published 2026-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 e-plugins Listihub listihub allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Listihub: from n/a through <= 1.0.6.

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 Listihub WordPress plugin allows attackers to exploit incorrectly configured access control security levels, potentially enabling unauthorized access to protected functionality or administrative features that should require proper authentication and authorization checks.

MitigationUpdate to the latest version of Listihub (1.0.7 or later) which should include proper authorization checks and access control validations. Until patched, restrict administrative access and monitor for suspicious activity.

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
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Verify Listihub plugin is installed
    Log in to WordPress admin panel, navigate to Plugins > Installed Plugins, and look for 'Listihub' in the list of active plugins
    Affected if Listihub plugin is present and active in the WordPress installation
  2. Check installed Listihub version
    In WordPress admin, go to Plugins > Installed Plugins, find Listihub, and note the version number displayed under the plugin name. Alternatively, check the plugin header in /wp-content/plugins/listihub/ directory by reading the main plugin file (usually listihub.php)
    Affected if The installed version is lower than 1.0.7 (versions prior to 1.0.7 lack proper authorization checks)
  3. Identify exposed administrative functions
    Review the Listihub plugin settings and features in the WordPress admin dashboard under the plugin menu. Look for any endpoints, AJAX actions, or admin pages that handle user data, settings modifications, or content management
    Affected if The plugin exposes administrative or user-management functions that could be accessed without proper authentication
  4. Check for unauthorized access indicators
    Review WordPress access logs and server logs for requests to Listihub plugin files or AJAX endpoints from unauthenticated IPs or non-admin users. Look for unusual POST requests to /wp-admin/admin-ajax.php with listihub-related action parameters
    Affected if Requests to Listihub functionality are observed from unauthenticated users or unauthorized IP addresses

A WordPress site running Listihub version below 1.0.7 is affected if the plugin is active and its administrative or user-facing features are accessible 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

Update to the latest version of Listihub (1.0.7 or later) which should include proper authorization checks and access control validations. Until patched, restrict administrative access and monitor for suspicious activity.

Recommended fix Moderate confidence

latest version available (1.0.7 or higher)

  1. Update the Listihub plugin to the latest available version from the WordPress plugin repository
  2. Navigate to Plugins > Installed Plugins in WordPress admin
  3. Locate Listihub and click Update Now if an update is available
  4. After updating, verify the plugin version in the plugins list
  5. Test critical functionality to ensure the authorization controls are working properly after the update

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation3.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,070
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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