EventON Action User <= 2.5.14 - Missing Authorization to Unauthenticated Privilege Escalation via evoau_save_capability AJAX Action
The EventON Action User plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 2.5.14. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to grant EventON management capabilities and the upload_files capability to any non-administrator WordPress role or user, escalating their privileges within the site. The administrator role is protected by an early-return guard in update_role_caps(), so only non-administrator roles and individual users can be targeted; however, the same unauthenticated exposure also allows attackers to enumerate all WordPress users with their IDs and display names, disclose role and user capability state along with nonce values, and tamper with event-to-user term assignments.
Browse WordPress security risksQuick answer
EventON Action User should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- <= 2.5.14
- up to and including 2.5.14
Fixed versions
- 2.5.15
How to fix it
CVE-2026-10033 affects EventON Action User and involves authorization failure. Successful exploitation may let a lower-privileged user view or change data outside their allowed scope. Treat this as a high-priority fix, especially when the affected component or endpoint is reachable by untrusted users. Upgrade EventON Action User to 2.5.15 or a later vendor-supported fixed release.
- Inventory every deployment, device, package, plugin, container, build, and environment that uses EventON Action User.
- Compare the installed version with the recorded affected range: <= 2.5.14, *-2.5.14.
- Upgrade EventON Action User to 2.5.15 or a later vendor-supported fixed release.
- Until patched, disable the affected EventON Action User feature or plugin and restrict its public and administrator endpoints.
- Review configuration, roles, tokens, network paths, and exposed endpoints connected to EventON Action User; remove access that is not required.
- Review authentication, API, audit, and object-change logs for cross-user access, bypassed checks, or unexpected privileged actions.
- If exploitation is suspected, isolate affected assets, preserve evidence, rotate exposed credentials or keys, restore trusted data, and rebuild compromised systems before returning them to service.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm every affected asset now runs the fixed vendor-supported release or has the documented mitigation for CVE-2026-10033 in place.
- Use a safe regression test to confirm the affected authorization failure path no longer produces the vulnerable behavior.
- Confirm temporary access controls, endpoint restrictions, network blocks, and least-privilege settings remain effective after the update.
- Review post-remediation logs and rerun Fixnx plus the relevant package, dependency, firmware, browser, or product-specific security check.
- Document affected assets, versions, changes, validation evidence, reviewed logs, and any credential rotation, cleanup, or replacement completed.
Related categories
Related security risks
More published guidance from the same primary category.
CVE-2026-65500 Manual - Documentation, Knowledge Base & Education WordPress Theme vulnerability
Updated July 24, 2026
highWPO365 | SEAMLESS WORDPRESS + MICROSOFT INTEGRATION (WPO365 | LOGIN) <= 43.2 - Cross-Site Request Forgery to Privilege Escalation via Plugin Settings Update
Updated July 24, 2026
mediumParticipants Database <= 2.7.8.3 - Missing Authorization to Unauthenticated Arbitrary Record Update / Sensitive Information Exposure via 'id' Parameter
Updated July 24, 2026
Trusted references
FAQ
What is affected by CVE-2026-10033?
EventON Action User versions listed as affected should be reviewed: <= 2.5.14, up to and including 2.5.14.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.