criticalCVE-2026-12761

miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) <= 7.7.0 - Unauthenticated Authentication Bypass to Administrator Account Takeover via Profile Completion OTP Flow

Q: 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.

Q: 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.

Q: 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.

The miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) plugin for WordPress is vulnerable to authentication bypass leading to account takeover in versions up to and including 7.7.0. This is due to the Profile Completion flow accepting an arbitrary email address via the 'email_field' POST parameter without verifying that the email belongs to the identity returned by the OAuth provider, combined with send_otp_token() returning the SHA-512(customer_key || otp) transaction hash to the client where the OTP space is only 99,000 values (wp_rand(1000, 99999)) and the customer_key is a static option (empty on unregistered installs). This makes it possible for unauthenticated attackers to trigger an OTP email to an arbitrary admin's address, crack the OTP offline from the leaked hash in under a second, and submit the cracked OTP to mo_openid_social_login_validate_otp(), which logs the attacker in as the user whose email was supplied — granting full administrator access.

ProductminiOrange Social Login and Register (Discord, Google, Twitter, LinkedIn)

CVSS9.8

EPSS0.00463

UpdatedJuly 13, 2026

Quick answer

miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) 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

*-7.7.0

Fixed versions

7.8.0

How to fix it

miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) is affected by CVE-2026-12761, a authentication bypass issue in versions up to 7.7.0. Wordfence lists the official remediation as updating to version 7.8.0, or a newer patched version. Prioritize internet-facing WordPress sites, sites with public registration, customer portals, Elementor/page-builder surfaces, and admin workflows where the vulnerable feature is enabled. If immediate patching is not possible, disable the affected plugin or feature, restrict access, and monitor for exploitation until the update is installed.

Inventory every WordPress site that has miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) installed, including production, staging, multisite, client, and WooCommerce environments.
Confirm the installed miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) version and compare it with the affected range from the Wordfence advisory.
Update miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) to version 7.8.0, or to a newer vendor-supported patched version from the official WordPress update channel.
If the update cannot be applied immediately, disable miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) or the affected feature and restrict access with roles, authentication, WAF rules, or temporary route blocking.
Review affected REST endpoints, AJAX actions, roles, capabilities, account changes, orders, bookings, payments, and admin actions for unauthorized activity.
Rotate administrator sessions, API keys, webhook secrets, payment or integration tokens, and affected credentials if logs or content review suggest compromise.
Clear WordPress, object, CDN, page-builder, security plugin, and browser caches after patching so vulnerable assets or stored payloads are not served.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

Confirm the running miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) version is version 7.8.0 or newer, and record the patched version in the remediation ticket.
Verify unauthenticated or low-privilege users can no longer trigger the affected action, endpoint, account, payment, booking, or settings change.
Review web server, WordPress, security plugin, WAF, database, and application logs for exploitation attempts before and after the fix.
Retest normal visitor, subscriber, customer, editor, administrator, checkout, form, API, booking, or integration workflows to confirm expected behavior still works.
Run a fresh Fixnx scan and document the public exposure state, patched version, log review, and any cleanup evidence.

Related categories

WordPress Authentication Bypass

Trusted references

Wordfence advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Source advisoryWordfence, NVD Wordfence advisoryWordfence, NVD

FAQ

What is affected by CVE-2026-12761?

miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn) versions listed as affected should be reviewed: *-7.7.0.

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.