dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-5018

HIGH · 7.1 CVSS v3.1 Published 2025-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/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
The Hive Support plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on the hs_update_ai_chat_settings() and hive_lite_support_get_all_binbox() functions in all versions up to, and including, 1.2.5. This makes it possible for authenticated attackers, with Subscriber-level access and above, to read and overwrite the site’s OpenAI API key and inspection data or modify AI-chat prompts and behavior. This vulnerability is potentially a duplicate of CVE-2025-32208 or/and CVE-2025-32242.

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 · high confidence

The Hive Support WordPress plugin is vulnerable to Broken Access Control due to missing capability checks on two AJAX functions (hs_update_ai_chat_settings and hive_lite_support_get_all_binbox). This allows any authenticated user with Subscriber-level permissions to read/write OpenAI API keys and modify AI chat prompts and behavior, bypassing normal authorization controls.

MitigationUpdate the Hive Support plugin to version 1.2.6 or later which includes proper capability checks. If immediate update is not possible, consider restricting user registration or removing Subscriber-level accounts.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Verify Hive Support plugin is installed
    Navigate to WordPress admin > Plugins and look for 'Hive Support' in the installed plugins list, or query the database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' and option_value LIKE '%hive-support%';
    Affected if Hive Support plugin is not found in the installation
  2. Determine installed plugin version
    In WordPress admin > Plugins > Hive Support, check the version number displayed under the plugin name. Alternatively, check the plugin header in wp-content/plugins/hive-support/hive-support.php for 'Version:' tag.
    Affected if Version is present but lower than 1.2.6 (the patched version)
  3. Confirm plugin is active
    In WordPress admin > Plugins, verify Hive Support shows as 'Active'. Also check: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins' AND option_value LIKE '%hive-support%';
    Affected if Plugin is installed but not active - not vulnerable in this state
  4. Check for existing user accounts with Subscriber role
    In WordPress admin > Users, review all users and their assigned roles. Any user with Subscriber, Contributor, Author, Editor, or Administrator role can exploit this vulnerability. Query: SELECT user_id, meta_value FROM wp_usermeta WHERE meta_key = 'wp_capabilities';
    Affected if At least one user account exists with Subscriber-level permissions or higher ( Contributor, Author, Editor, Admin )
  5. Verify AI chat settings functionality exists
    Check if the plugin has AI chat configuration options accessible. Look for menu items like 'Hive Support > AI Settings' or 'Chat Settings' in the admin panel, or inspect if hs_update_ai_chat_settings AJAX action is registered in the plugin code.
    Affected if The AI chat settings interface is present in the admin panel

User is affected if Hive Support plugin is installed, active, version is below 1.2.6, and at least one user account with Subscriber-level or higher access exists in WordPress.

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 the Hive Support plugin to version 1.2.6 or later which includes proper capability checks. If immediate update is not possible, consider restricting user registration or removing Subscriber-level accounts.

Recommended fix Moderate confidence

1.2.6 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Find the Hive Support plugin
  4. If an update is available, click 'Update Now' to install the latest version
  5. Alternatively, download the latest version from wordpress.org/plugins/hive-support and upload it manually via Plugins > Add New > Upload Plugin
  6. After updating, verify the plugin version is 1.2.6 or higher in the plugins list

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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