dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-68059

HIGH · 7.6 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 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 Hotel Listing hotel-listing allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Hotel Listing: from n/a through <= 1.4.2.

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 e-plugins Hotel Listing WordPress plugin (versions <= 1.4.2) contains a missing authorization vulnerability where certain functions or data endpoints lack proper access control checks. This allows lower-privileged users or unauthenticated actors to access functionality intended for higher security levels due to incorrectly configured security level settings in the plugin's access control mechanism.

MitigationImplement proper authorization checks (capability/permission verifications) on all sensitive plugin functions and data endpoints, ensuring that the plugin correctly enforces WordPress user role-based access controls. Update to the latest plugin version once available.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/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. Check plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins > locate e-plugins Hotel Listing and verify the version number displayed in the plugin metadata
    Affected if The installed version is 1.4.2 or lower
  2. Confirm plugin is active
    Verify the e-plugins Hotel Listing plugin shows as 'Active' in the WordPress plugins admin list
    Affected if Plugin is active and version is <= 1.4.2
  3. Test low-privilege user access
    Log in with a WordPress user account that has only the Subscriber role and attempt to access plugin admin pages (typically under a menu item like Hotel Listing or similar in the wp-admin sidebar) or trigger plugin AJAX actions via admin-ajax.php
    Affected if A Subscriber-level user can access plugin administrative functions or view hotel listing data intended for administrators
  4. Test unauthenticated access
    Send a direct HTTP request to plugin AJAX endpoints (admin-ajax.php?action=hotel_listing_* or similar actions the plugin registers) without providing any authentication cookies or credentials
    Affected if Unauthenticated requests successfully execute plugin functions or return data that should require authorization

Environment is affected if the plugin version is 1.4.2 or lower AND either low-privileged WordPress users or unauthenticated visitors can access plugin functions intended only for administrators.

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

Implement proper authorization checks (capability/permission verifications) on all sensitive plugin functions and data endpoints, ensuring that the plugin correctly enforces WordPress user role-based access controls. Update to the latest plugin version once available.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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