# CVE-2026-13597: QRcode Login for WeChat <= 1.3 - Unauthenticated Account Takeover

> Unauthenticated attackers can bypass WeChat login validation to take over any user account, including administrators, in the QRcode Login plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2026
- **Updated:** 27 Jul 2026
- **Also known as:** GHSA-p6m4-vx92-q2pc

## What is CVE-2026-13597?

CVE-2026-13597 is a critical authentication bypass vulnerability in Unknown 微信二维码登陆, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The 微信二维码登陆 WordPress plugin through 1.3 does not properly validate WeChat webhook requests, as its signature check always passes, and it discloses the generated login code in the webhook response. This allows an unauthenticated attacker to forge a login event for any existing username, read the login code, and redeem it through an unauthenticated AJAX action to log in as that user, including an administrator, without a password.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-13597?


## How do I fix CVE-2026-13597?

No fix has been published for CVE-2026-13597 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13597 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13597 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13597 and fix it if it is affected.

What it is: CVE-2026-13597 is a critical authentication bypass vulnerability in Unknown 微信二维码登陆, published on 27 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13597 exists.

Affected product: Unknown 微信二维码登陆. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13597/ (Markdown: https://insights.sbomify.com/CVE-2026-13597/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13597
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13597
- OSV: https://osv.dev/vulnerability/CVE-2026-13597

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13597/
Summaries are generated and may contain mistakes; the official description above is the record.
