QRcode Login for WeChat <= 1.3 - Unauthenticated Privilege Escalation via Account Takeover
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- 微信二维码登陆
- Affected Version
<= 1.3- CVSS
- 9.8Critical
- Weakness type
- CWE-287 · Improper Authentication
- CVE
CVE-2026-13597
At a glance
CVE-2026-13597 is a critical-severity Improper Authentication vulnerability in the 微信二维码登陆 WordPress plugin, affecting versions <= 1.3. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed July 2026, reported by João Ramos Maciel.
Vulnerability Overview
The QRcode Login for WeChat plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 1.3. This makes it possible for unauthenticated attackers to authenticate as other users, including administrators.
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
Reaching this weakness in 微信二维码登陆 <= 1.3 takes no account at all. 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. No fixed build of this plugin is recorded for 微信二维码登陆 yet, so installs running <= 1.3 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C