Loading story…
Three high-severity flaws in LoginPress Pro for WordPress can let unauthenticated attackers log in as existing site users, including administrators, by abusing weaknesses in the plugin’s OAuth-based social login flows. The issues, tracked as CVE-2026-12595, CVE-2026-12597, and CVE-2026-12598, affect versions through 6.2.3 and carry CVSS 8.1 ratings. Researchers said the free version of LoginPress is not affected, while the premium plugin has more than 50,000 active installations.
The bypasses stem from insufficient verification of email data returned by OAuth providers. In the GitHub flow, the plugin trusts the first email returned by the /user/emails endpoint without confirming it is verified, while the Spotify Social Login addon accepts the email from Spotify’s /v1/me endpoint and uses it to identify and authenticate WordPress users. An attacker can add or create a matching email address on a third-party account and then trigger the OAuth callback to gain access as the targeted WordPress user. The vulnerabilities were disclosed through Patchstack, credited to Dmitrii Ignatyev, and fixed in LoginPress Pro 6.2.4; organizations that cannot patch immediately are advised to disable affected social login features.
See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
The CVE entry for CVE-2026-12598 was received by security@wordfence.com. The vulnerability covers an unauthenticated authentication bypass in the Spotify Social Login addon caused by trusting an unverified email from Spotify's /v1/me endpoint.
The vulnerabilities affecting LoginPress Pro up to version 6.2.3 were fixed in version 6.2.4 and later. Guidance in the references recommends updating to 6.2.4 or disabling affected social login features if patching is not immediately possible.
The three LoginPress Pro vulnerabilities, tracked as CVE-2026-12595, CVE-2026-12597, and CVE-2026-12598, were disclosed through Patchstack. The issues can allow unauthenticated attackers to take over WordPress accounts, including administrator accounts.
Dmitrii Ignatyev discovered three high-severity authentication bypass vulnerabilities in LoginPress Pro affecting versions up to and including 6.2.3. The flaws stem from insufficient verification in OAuth-based social login flows, including GitHub and Spotify email handling.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cvefeed.io
Open sourcecvefeed.io
Open sourcethreataft.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Multiple critical flaws in widely deployed WordPress plugins exposed sites to administrator takeover through broken REST API authorization, weak JWT handling, and sensitive data leakage. In **Post SMTP**, `CVE-2025-24000` let any authenticated user read administrator-only email logs in versions through `3.2.0`, while `CVE-2025-11833` extended similar exposure to unauthenticated attackers in versions through `3.6.0`; because password reset messages were stored in those logs, attackers could reset admin passwords and seize control of affected sites. **RestroPress** (`CVE-2025-9209`) exposed user tokens through `/wp-json/wp/v2/users`, enabling forged JWTs and full admin access, and **miniOrange OAuth SSO** (`CVE-2025-9485`) accepted forged JWTs because signatures were not verified, allowing login as arbitrary users including administrators. **Copypress Rest API** (`CVE-2025-8625`) combined a hard-coded JWT signing key with unrestricted file upload to enable unauthenticated remote code execution. The pattern continued into active exploitation of **Gravity SMTP** (`CVE-2026-4020`), where an unauthenticated REST API endpoint exposed system reports containing WordPress and server details, plugin inventories, database information, and email-service credentials such as API keys, secrets, and OAuth tokens. Wordfence said exploitation required only a single request, reported blocking more than **17 million** attempts, and urged defenders to upgrade to `2.1.5` and rotate exposed third-party email credentials. Across the affected plugins, vendors issued fixes including **Post SMTP 3.3.0**, **miniOrange 6.26.13**, and **Gravity SMTP 2.1.5**, while the Copypress plugin was temporarily closed; the incidents underscore how exposed REST endpoints and flawed token validation can quickly turn routine plugin features into full site compromise paths.
Jun 29, 2026
A critical authentication bypass vulnerability, **CVE-2024-10924**, was disclosed and fixed in the WordPress plugin **Really Simple Security**, affecting the Free, Pro, and Pro Multisite editions in versions `9.0.0` through `9.1.1.1`. The flaw carries a **CVSS 9.8** rating and can allow an unauthenticated attacker to log in as any user, including an administrator, on sites where the plugin’s two-factor authentication feature is enabled. The issue was traced to improper error handling in the `check_login_and_get_user` function within the plugin’s two-factor authentication REST API. Defenders warned that roughly **4 million** websites could be exposed, making the bug a high-priority patching issue for WordPress operators. Site owners were urged to update immediately to **version 9.1.2 or later** to close the vulnerability.
Jul 24, 2026
Multiple high-severity flaws in WordPress plugins exposed sites to account takeover and, in one case, possible remote code execution. In **Users Manager PN**, tracked as `CVE-2026-4003`, a missing authorization check in the `userspn_ajax_nopriv_server()` handler let unauthenticated attackers overwrite arbitrary user metadata through the `userspn_form_save` AJAX action. Because the required `userspn-nonce` was reportedly exposed on public pages, attackers could abuse the bug with a single crafted request to modify profiles and potentially seize control of administrator accounts. The issue affected versions through `1.1.15` and was reportedly fixed in `1.1.20`. Two additional vulnerabilities were disclosed in **WP Captcha PRO** affecting versions through `5.38`. `CVE-2026-5415` allowed **Subscriber-level users or higher** to generate temporary login links for arbitrary accounts because the `ajax_run_tool()` AJAX handler checked only a nonce and not user capabilities, enabling authentication bypass and administrator takeover. Separately, `CVE-2026-5411` allowed authenticated low-privilege users to upload attacker-controlled files by poisoning license metadata and abusing `sync_cloud_protection()` to download and extract content into a web-accessible uploads directory; if PHP execution was possible and `allow_url_fopen` was enabled for remote retrieval, the flaw could be escalated to **remote code execution** via a webshell.
Jun 29, 2026