Skip to main content
Vulnerability Database/CVE-2025-60123

CVE-2025-60123: HivePress Claim Listings Auth Bypass Flaw

CVE-2025-60123 is an authorization bypass vulnerability in HivePress Claim Listings that allows attackers to exploit misconfigured access controls. This article covers the technical details, affected versions up to 1.1.3, security impact, and recommended mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2025-60123 Overview

CVE-2025-60123 is a missing authorization vulnerability in the HivePress Claim Listings plugin for WordPress. The flaw affects all plugin versions up to and including 1.1.3. It stems from incorrectly configured access control security levels [CWE-862], allowing authenticated users with low privileges to perform actions reserved for higher-privileged roles. The vulnerability is network-exploitable and requires only basic authenticated access, with no user interaction. Attackers abusing this flaw can achieve limited integrity impact on affected WordPress installations running the HivePress Claim Listings extension.

Critical Impact

Authenticated low-privilege users can bypass access controls in the HivePress Claim Listings plugin to perform unauthorized actions against listing claim functionality.

Affected Products

  • HivePress Claim Listings plugin for WordPress
  • All versions from initial release through 1.1.3
  • WordPress sites using the hivepress-claim-listings extension

Discovery Timeline

  • 2025-09-26 - CVE-2025-60123 published to NVD
  • 2026-10-11 - Last updated in NVD database

Technical Details for CVE-2025-60123

Vulnerability Analysis

The HivePress Claim Listings plugin extends the HivePress directory framework by enabling users to claim ownership of business listings. The plugin exposes functionality through authenticated endpoints that should enforce role-based access control. The vulnerability allows an authenticated attacker to interact with functionality intended for other users or elevated roles.

The flaw is classified under CWE-862: Missing Authorization. The affected code paths perform authentication checks but fail to validate whether the authenticated principal is authorized to execute the requested operation. This separation between authentication and authorization is a common WordPress plugin weakness.

Successful exploitation yields limited integrity impact without affecting confidentiality or availability. The attack surface is accessible over the network through standard WordPress HTTP endpoints.

Root Cause

The root cause is incorrectly configured access control security levels within plugin request handlers. The plugin verifies that a user is logged in but does not consistently check capability or ownership before executing privileged operations tied to listing claims.

Attack Vector

An attacker authenticates to the WordPress site as any low-privilege user, including a subscriber-level account where open registration is enabled. The attacker then issues HTTP requests to the plugin's claim-related endpoints with parameters targeting resources they do not own. Because the handlers skip authorization validation, the plugin processes the request and modifies state. Technical details are documented in the Patchstack HivePress Vulnerability Report.

Detect Identity Attacks the Moment Authentication Fails

Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.

Stop Identity Attacks

Detection Methods for CVE-2025-60123

Indicators of Compromise

  • Unexpected modifications to listing claim records attributed to low-privilege accounts
  • HTTP POST requests to HivePress claim endpoints originating from subscriber-role sessions
  • Database rows in HivePress claim tables referencing user IDs that do not match the listing owner
  • Surges in newly registered accounts followed by requests to /wp-admin/admin-ajax.php with HivePress action parameters

Detection Strategies

  • Audit WordPress access logs for authenticated requests targeting the hivepress-claim-listings plugin endpoints and correlate user roles with action parameters
  • Enable WordPress audit logging plugins to record claim submission, approval, and rejection events along with the acting user ID
  • Compare current plugin version against 1.1.3 across all managed WordPress instances to identify vulnerable installations

Monitoring Recommendations

  • Monitor admin-ajax.php and REST API traffic for high request volumes from low-privilege accounts
  • Track changes to listing ownership and claim status in the HivePress data model and alert on anomalies
  • Alert on new user registrations immediately followed by claim-related API activity within short time windows

How to Mitigate CVE-2025-60123

Immediate Actions Required

  • Inventory all WordPress sites to identify installations of the HivePress Claim Listings plugin at version 1.1.3 or earlier
  • Update the plugin to a version later than 1.1.3 as soon as the vendor releases a patched release
  • Review listing claim records for unauthorized modifications and revert any suspicious entries
  • Disable open user registration where it is not required for business operations

Patch Information

At the time of publication, the advisory indicates the vulnerability affects HivePress Claim Listings versions up to and including 1.1.3. Administrators should consult the Patchstack advisory and the HivePress vendor channel for the fixed version and apply it across all affected sites.

Workarounds

  • Deactivate the HivePress Claim Listings plugin until a patched version is installed if the claim functionality is not business-critical
  • Restrict access to the plugin's endpoints at the web application firewall (WAF) layer by blocking requests from low-privilege session cookies to claim action parameters
  • Enforce stricter role assignment and avoid granting the default subscriber role capabilities that interact with HivePress claim operations
bash
# Example WAF rule concept: block authenticated subscriber-role requests
# targeting HivePress claim actions until the plugin is patched
# (adapt to your WAF syntax)
SecRule REQUEST_URI "@contains /wp-admin/admin-ajax.php" \
  "chain,deny,status:403,id:1060123,msg:'Block HivePress claim action for low-privilege users'"
  SecRule ARGS:action "@rx ^hivepress/.*claim.*" \
    "chain"
    SecRule REQUEST_COOKIES:/wordpress_logged_in_/ "@rx .+"

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.