RingCentral Communications 1.5 - 1.6.8 - Missing Server‑Side Verification to Authentication Bypass via ringcentral_admin_login_2fa_verify Function
Strategic Overview
- Status
- Patched in 1.7.0
- Affected Plugin
- RingCentral Communications Plugin – FREE
- Affected Version
1.5 – 1.6.8- CVSS
- 9.8Critical
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2025-7955
At a glance
CVE-2025-7955 is a critical-severity Improper Authentication vulnerability in the RingCentral Communications Plugin WordPress plugin, affecting versions 1.5 – 1.6.8. 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.7.0; sites on affected versions should update now. Disclosed August 2025, reported by kr0d.
Vulnerability Overview
The RingCentral Communications plugin for WordPress is vulnerable to Authentication Bypass due to improper validation within the ringcentral_admin_login_2fa_verify() function in versions 1.5 to 1.6.8. This makes it possible for unauthenticated attackers to log in as any user simply by supplying identical bogus codes.
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-287: Improper Authentication
RingCentral Communications Plugin 1.5 – 1.6.8 carries this weakness at ringcentral_admin_login_2fa_verify(), and reaching it takes a caller who can reach the endpoint. Improper authentication means the mechanism that proves who a caller is can be satisfied without the secret it was supposed to require.
An attacker authenticates as another user — administrators included — without ever knowing a password, so password policies and login rate limits never come into play. For RingCentral Communications Plugin the fix is 1.7.0: builds 1.5 – 1.6.8 are affected, anything from 1.7.0 onward is not.
Remediation
Update to version 1.7.0, 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: RingCentral Communications Plugin 1.7.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in RingCentral Communications Plugin – FREE
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C