dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-30790

MEDIUM · 5.3 CVSS v3.1 Published 2025-03-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 alexvtn Chatbox Manager wa-chatbox-manager allows Accessing Functionality Not Properly Constrained by ACLs.This issue affects Chatbox Manager: from n/a through <= 1.2.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

Missing authorization vulnerability in the wa-chatbox-manager WordPress plugin allows users to access functionality that should be restricted by Access Control Lists (ACL). The plugin fails to properly validate user permissions before executing certain functions, potentially permitting unauthenticated or lower-privileged users to perform actions that should require higher privilege levels.

MitigationImplement proper role-based access control (RBAC) checks on all sensitive functions and endpoints within the plugin. Update to the latest patched version when available, and audit all existing ACL constraints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 wa-chatbox-manager plugin is installed
    Navigate to WordPress admin > Plugins and confirm 'wa-chatbox-manager' appears in the list, or check the /wp-content/plugins/ directory for a folder named 'wa-chatbox-manager' or similar
    Affected if the plugin is installed and active
  2. Identify the installed plugin version
    Open the plugin's main PHP file (typically wa-chatbox-manager.php) and locate the 'Version' header in the plugin comment block, or check version in readme.txt
    Affected if the installed version is lower than the patched version (compare against vendor release notes)
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify the plugin shows as 'Active'
    Affected if the plugin is currently active in the WordPress installation
  4. Test for missing authorization on plugin endpoints
    Attempt to access plugin admin pages or AJAX actions while logged out or as a low-privilege user (subscriber), checking if requests are rejected with proper permission errors or proceed without authentication
    Affected if requests to plugin functions complete successfully without proper capability checks or authentication
  5. Inspect plugin code for capability checks
    Review the plugin's PHP files for current_user_can(), wp_verify_nonce(), or similar authorization calls before sensitive operations, focusing on AJAX handlers and admin menu callbacks
    Affected if sensitive functions lack proper capability verification or nonce validation

A user is affected if the wa-chatbox-manager plugin is installed, active, and exposes functionality that can be accessed without proper authentication or 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

Implement proper role-based access control (RBAC) checks on all sensitive functions and endpoints within the plugin. Update to the latest patched version when available, and audit all existing ACL constraints.

Recommended fix Moderate confidence

Version 1.2.3 or latest stable release

  1. 1. Back up your WordPress site and database before making any changes.
  2. 2. Navigate to the WordPress admin dashboard > Plugins.
  3. 3. Locate the 'Chatbox Manager' (wa-chatbox-manager) plugin by alexvtn.
  4. 4. If an update is available, click 'Update Now' to install the latest version.
  5. 5. If no update appears in the WordPress admin, visit the WordPress Plugin Repository or the vendor's website to download the latest version.
  6. 6. Deactivate the current plugin, delete it, then upload and install the new version.
  7. 7. Reactivate the plugin and verify that the chatbox functionality works correctly.
  8. 8. Test that the authorization controls are properly enforced (e.g., ensure only authorized users can access chatbox management features).

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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