dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2025-66082

MEDIUM · 5.3 CVSS v3.1 Published 2025-11-21
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 magepeopleteam WpEvently mage-eventpress allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects WpEvently: from n/a through <= 5.0.4.

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 WpEvently WordPress plugin allows attackers to exploit incorrectly configured access control security levels. The vulnerability exists in versions up to and including 5.0.4, permitting unauthorized access to functionality or data that should require proper authentication and authorization checks.

MitigationUpdate WpEvently to the latest patched version when available, and review the plugin's access control configuration to ensure all sensitive functions and endpoints enforce proper authorization checks.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Check WpEvently plugin version
    Log in to WordPress admin, navigate to Plugins > Installed Plugins, locate WpEvently, and note the version number displayed. Alternatively, access the plugin directory via FTP or file manager and open the main plugin file (typically wpevently.php) to read the Version header in the plugin comment block.
    Affected if The displayed version is 5.0.4 or lower (any version up to and including 5.0.4)
  2. Identify sensitive plugin functions or endpoints
    Review the WpEvently plugin directory for PHP files containing sensitive operations such as data exports, user management, event creation/modification, or settings changes. Common indicators include AJAX handlers (wp_ajax_ hooks), REST API endpoints, or form processing files.
    Affected if The plugin contains functions handling sensitive data or administrative actions without visible capability checks or nonce verification
  3. Test endpoint accessibility without authentication
    Using a browser or HTTP tool (such as curl), attempt to access suspected sensitive endpoints or trigger AJAX actions provided by the plugin while logged out. For example, check if URLs containing 'wpevently', 'admin-ajax.php?action=wpevently_...' or REST API routes '/wp-json/wpevently/...' respond without requiring authentication.
    Affected if The endpoint returns expected data or performs actions without redirecting to a login page or returning an authorization error
  4. Verify access control configuration
    Examine the plugin source code for proper authorization checks before executing sensitive operations. Look for functions like current_user_can(), wp_verify_nonce(), or is_user_logged_in() placed at the beginning of functions handling data or administrative actions.
    Affected if Sensitive functions lack these authorization checks or the checks are present but incorrectly implemented (e.g., missing capability verification)

Your environment is affected if the WpEvently plugin version is 5.0.4 or lower AND sensitive plugin functions or endpoints are accessible without authentication or proper capability 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WpEvently to the latest patched version when available, and review the plugin's access control configuration to ensure all sensitive functions and endpoints enforce proper authorization checks.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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