CVE-2023-35777
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 · uneditedMissing Authorization vulnerability in The Events Calendar The Events Calendar allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects The Events Calendar: from n/a through 6.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 confidenceMissing authorization vulnerability in The Events Calendar WordPress plugin allows users to access functionality they shouldn't have permission to access due to incorrectly configured access control security levels. The plugin fails to properly validate user capabilities before allowing access to certain sensitive operations.
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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installationCheck if The Events Calendar plugin files exist in the WordPress plugins directory (wp-content/plugins/the-events-calendar/) or list installed plugins via WordPress admin under Plugins > Installed PluginsAffected if The Events Calendar plugin is not found in the installation
-
Determine installed versionOpen the main plugin file (the-events-calendar.php) in the plugin directory and locate the 'Version' header comment, or check the version displayed in WordPress admin Plugins listAffected if The installed version is not the latest and may be among affected versions (compare against known vulnerable versions for this CVE)
-
Confirm user role configurationNavigate to Users > All Users in WordPress admin and review which users have Editor, Author, Contributor, or Subscriber roles, noting any unexpected administrative accessAffected if Lower-privileged users (Authors, Contributors) exist on the site who could potentially exploit the missing capability check
-
Test sensitive operation accessUsing a limited-user account (such as an Author or Contributor), attempt to access The Events Calendar admin pages or REST API endpoints for event management that should require Administrator privilegesAffected if A non-administrator user can access or modify calendar settings, events, or other sensitive data they should not have permission to modify
-
Review capability configurationCheck the plugin's access control settings under Events > Settings > General to see if any capability restrictions are defined, and inspect the plugin code for 'current_user_can' or 'map_meta_cap' capability checks around sensitive functionsAffected if No capability checks are found in the plugin code before sensitive operations, or users without proper roles can perform administrative tasks
The environment is affected if The Events Calendar plugin is installed AND the installed version matches vulnerable versions AND lower-privileged users can access administrative functionality they should not have access to.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement proper capability checks and access control validation on all sensitive plugin operations and admin functionality to ensure users can only access resources they're authorized for.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-35777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-35777 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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