dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-67977

HIGH · 8.2 CVSS v3.1 Published 2026-02-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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 VillaTheme HAPPY happy-helpdesk-support-ticket-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects HAPPY: from n/a through <= 1.0.8.

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

A missing authorization vulnerability in the VillaTheme HAPPY helpdesk support ticket system (version <= 1.0.8) allows attackers to exploit incorrectly configured access control security levels. The vulnerability stems from insufficient authorization checks, likely enabling unauthorized users to access ticket data, perform administrative actions, or view/modify tickets outside their intended permissions.

MitigationImplement proper role-based authorization checks on all sensitive endpoints and actions within the ticket system. Verify that users can only access tickets and perform actions permitted by their security level.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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. Confirm HAPPY plugin installation
    Locate the VillaTheme HAPPY helpdesk plugin in the WordPress plugins directory (wp-content/plugins/) or check via WordPress admin panel under Plugins
    Affected if The HAPPY helpdesk plugin is present in the installation
  2. Identify installed version
    Check the plugin header in happy.php main file or view version in WordPress plugin admin list; compare against the affected range <= 1.0.8
    Affected if Installed version is 1.0.8 or lower
  3. Inspect user role configuration
    Review WordPress user roles and HAPPY-specific user level settings under the plugin settings panel; check if custom roles have been assigned elevated permissions
    Affected if Users are assigned roles that grant access beyond their intended permission level
  4. Verify ticket access controls
    Test accessing ticket endpoints (such as ticket view/modify URLs) with a low-privilege or unauthorized user account to confirm proper authorization enforcement
    Affected if Lower-privilege or unauthorized users can view, modify, or access tickets outside their permitted scope
  5. Audit administrative actions
    Log actions performed by non-administrator users on ticket management functions (create, close, delete, assign tickets) and verify each requires proper authorization
    Affected if Non-administrator users can perform administrative ticket actions without proper role-based checks

Environment is affected if the HAPPY helpdesk plugin version 1.0.8 or lower is installed and users with insufficient privileges can access or modify tickets beyond their authorized scope due to missing 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 authorization checks on all sensitive endpoints and actions within the ticket system. Verify that users can only access tickets and perform actions permitted by their security level.

Recommended fix Moderate confidence

Update to a version greater than 1.0.8 (latest available version from VillaTheme)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the HAPPY happy-helpdesk-support-ticket-system plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to the latest secure version
  5. 5. Verify the plugin was updated to a version newer than 1.0.8
  6. 6. Test the helpdesk functionality to ensure the update did not break existing features
Caveat Unknown - minor version update unlikely to have breaking changes, but test in staging first

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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