Event List <= 2.0.4 - Authenticated (Subscriber+) Privilege Escalation
Strategic Overview
- Status
- Patched in 2.0.5
- Affected Plugin
- Event List
- Affected Version
<= 2.0.4- CVSS
- 8.8High
- Weakness type
- CWE-269 · Improper Privilege Management
- CVE
CVE-2025-6366
At a glance
CVE-2025-6366 is a high-severity Improper Privilege Management vulnerability in the Event List WordPress plugin, affecting versions <= 2.0.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.0.5; sites on affected versions should update now. Disclosed August 2025, reported by Tonn.
Vulnerability Overview
The 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 Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-269: Improper Privilege Management
Event List <= 2.0.4 carries this weakness at el_update_profile(), and reaching it takes an account at Subscriber level or above. Improper privilege management means the code lets an account end up with capabilities its role should not have.
It converts a low-privileged account into an administrative one, which makes every other restriction on the site irrelevant. For Event List the fix is 2.0.5: builds <= 2.0.4 are affected, anything from 2.0.5 onward is not.
Remediation
Update to version 2.0.5, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Event List 2.0.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Event List
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C