dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-5019

MEDIUM · 5.4 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 →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

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 | AI-Powered Help Desk, Live Chat & AI Chat Bot Plugin for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.5. This is due to missing or incorrect nonce validation on the hs_update_ai_chat_settings() function. This makes it possible for unauthenticated attackers to reconfigure the plugin’s AI/chat settings (including API keys) and to potentially redirect notifications or leak data to attacker-controlled endpoints via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 Cross-Site Request Forgery (CSRF) due to missing or incorrect nonce validation on the hs_update_ai_chat_settings() function. This allows unauthenticated attackers to forge administrative requests and modify AI/chat configuration settings, including API keys, and potentially redirect notifications or exfiltrate data to attacker-controlled endpoints.

MitigationImplement proper nonce validation on the hs_update_ai_chat_settings() function and all state-changing operations. Additionally, add SameSite cookie attributes and consider implementing a CSRF token mechanism for sensitive admin actions.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/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. Locate the Hive Support plugin
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'hive-support' or similar. In the WordPress admin, go to Plugins > Installed Plugins and look for 'The Hive Support' or 'Hive Support' in the list.
    Affected if The plugin is installed and active in WordPress.
  2. Identify the installed plugin version
    In WordPress admin, find the plugin in Plugins > Installed Plugins. Click on the plugin name to view details, or inspect the plugin's main PHP file header for the 'Version' comment. Alternatively, check the readme.txt file in the plugin folder for the version number.
    Affected if A version of the plugin is installed (no specific safe version is documented in this CVE).
  3. Locate the vulnerable function
    In the plugin folder, search for the function 'hs_update_ai_chat_settings' in PHP files. This is typically found in admin settings files or files handling AJAX requests for chat/AI configuration.
    Affected if The function hs_update_ai_chat_settings exists in the plugin code.
  4. Inspect nonce validation in the function
    Open the PHP file containing hs_update_ai_chat_settings. Look for the presence of wp_verify_nonce, check_admin_referer, or similar nonce verification calls within this function. Also check if the function is hooked to an action that validates nonces.
    Affected if The function lacks proper nonce verification (no wp_verify_nonce, check_admin_referer, or nonce_field usage), indicating it is vulnerable to CSRF.
  5. Verify admin action accessibility
    Check if the function is hooked to admin_init, admin_post, or a similar WordPress admin action without requiring authentication checks. Look for add_action calls like 'admin_post_hs_update_ai_chat_settings' or similar.
    Affected if The function can be triggered via a forged request without the admin being logged in or without proper token validation.

Your environment is affected if the Hive Support WordPress plugin is installed and the hs_update_ai_chat_settings function lacks proper nonce validation, allowing unauthenticated attackers to forge administrative configuration changes.

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

Implement proper nonce validation on the hs_update_ai_chat_settings() function and all state-changing operations. Additionally, add SameSite cookie attributes and consider implementing a CSRF token mechanism for sensitive admin actions.

Recommended fix Moderate confidence

Version 1.2.6 or later

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'Hive Support | AI-Powered Help Desk, Live Chat & AI Chat Bot'
  4. Check the current version is 1.2.5 or below
  5. Click 'Update now' if an update is available, or manually download the latest version from wordpress.org
  6. After updating, verify the plugin version shows 1.2.6 or higher
  7. Review the AI chat settings to ensure no unauthorized changes were made to API keys or notification endpoints

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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