CVE-2025-6366
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 · uneditedThe Event List plugin for WordPress is vulnerable to privilege escalation in all versions up to, and including, 2.0.4. This is due to the plugin not properly validating a user's capabilities prior to updating their profile in the el_update_profile() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to change their capabilities to those of an administrator.
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 · high confidenceThe Event List WordPress plugin fails to validate user capabilities in the el_update_profile() function, allowing any authenticated user with Subscriber-level access or higher to modify their own user role and capabilities to Administrator level, achieving full site control.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 Event List plugin is installedNavigate to WordPress admin > Plugins and confirm the Event List plugin is present and active, or check the plugins directory (wp-content/plugins) for the event-list folderAffected if The Event List plugin is installed and active
-
Check installed plugin versionIn WordPress admin > Plugins > Installed Plugins, locate Event List and note the version number. Compare this against version 2.0.5 (the fixed version)Affected if Installed version is lower than 2.0.5 or version cannot be verified
-
Confirm user registration is enabledGo to WordPress admin > Settings > General and check if the 'Anyone can register' option is enabled, noting which default role is set (typically Subscriber)Affected if Anyone can register is enabled, allowing attackers to create Subscriber-level accounts
-
Audit user accounts for unauthorized Administrator rolesIn WordPress admin > Users, review all accounts with Administrator role. Check for unexpected accounts or those created recently that you do not recognizeAffected if There are Administrator accounts that were created without proper authorization
The environment is affected if the Event List plugin is installed with a version below 2.0.5 and user registration is open, allowing any Subscriber to escalate privileges to Administrator
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.
dbcve · scopedUpdate to version 2.0.5 or later when available. Until then, disable new user registration or audit existing user accounts for unauthorized privilege escalation.
Event List plugin version 2.0.5 or later
- Navigate to the WordPress admin dashboard
- Go to Plugins > Installed Plugins
- Locate the 'Event List' plugin
- Check if the current version is 2.0.4 or below
- If vulnerable, click 'Update Now' to update to the latest version
- Alternatively, download the latest version from wordpress.org or the vendor and upload via Plugins > Add New > Upload Plugin
- Verify the update completed successfully and the new version is 2.0.5 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-6366 — 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-2025-6366 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