WordPress WpEvently plugin <= 5.5.0 - Broken Access Control vulnerability

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps Magepeople inc./WpEvently (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for Magepeople inc./WpEvently.
2. 2Review the reported fix. Monitor this advisory for an available fix and review any installs of the affected package.

Evidence timeline and material changes

1. Published upstream

   Aug 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Aug 28, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Aug 28, 2026

Sources and claim methodology

• Source referencepatchstack.com

Related CVEs

• WordPress WpEvently plugin <= 5.5.0 - Broken Access Control vulnerabilitySame magepeople inc./wpevently package
• Hatchet allows cross-tenant write/DoS to other tenants' workers via Dispatcher gRPC UpsertWorkerLabels and UnsubscribeAlso CWE-862
• WordPress ACF Extended plugin <= 0.9.2.6 - Broken Access Control vulnerabilityAlso CWE-862
• WordPress Simple Payment plugin <= 2.5.2 - Broken Access Control vulnerabilityAlso CWE-862
• Pega Platform versions 7.1.0 through 25.1.2 are affected by an improper validation of inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.Same generic ecosystem
• morgan vulnerable to Log Forging via unescaped Unicode line separatorsSame generic ecosystem