Elated Membership <= 1.2 - Authentication Bypass via Social Login
Strategic Overview
- Status
- Patched in 1.3
- Affected Plugin
- Elated Membership
- Affected Version
<= 1.2- CVSS
- 9.8Critical
- Weakness type
- CWE-289 · Authentication Bypass by Alternate Name
- CVE
CVE-2025-13613
At a glance
CVE-2025-13613 is a critical-severity Authentication Bypass by Alternate Name vulnerability in the Elated Membership WordPress plugin, affecting versions <= 1.2. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.3; sites on affected versions should update now. Disclosed December 2025, reported by Foxyyy.
Vulnerability Overview
The Elated Membership plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 1.2. This is due to the plugin not properly logging in a user with the data that was previously verified through the 'eltdf_membership_check_facebook_user' and the 'eltdf_membership_login_user_from_social_network' function. This makes it possible for unauthenticated attackers to log in as administrative users, as long as they have an existing account on the site which can easily be created by default through the temp user functionality, and access to the administrative user's email.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-289: Authentication Bypass by Alternate Name
Elated Membership <= 1.2 carries this weakness at eltdf_membership_check_facebook_user, and reaching it takes a caller who can reach the endpoint. Authentication bypass by alternate name means access checks are performed against one form of an identifier while the sensitive operation uses another, so a differently spelled value slips through.
Registering or supplying a variant spelling of a privileged account's identifier is enough to be treated as that account. For Elated Membership the fix is 1.3: builds <= 1.2 are affected, anything from 1.3 onward is not.
Remediation
Update to version 1.3, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: Elated Membership 1.3 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C