# CVE-2018-20422: Auth bypass in n/a

> Remote attackers can bypass authentication and access arbitrary accounts when WeChat login is enabled in Discuz!.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-53cv-6j2x-jm64

## What is CVE-2018-20422?

CVE-2018-20422 is a high-severity authentication bypass vulnerability in n/a, published on 24 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Discuz! DiscuzX 3.4, when WeChat login is enabled, allows remote attackers to bypass authentication by leveraging a non-empty #wechat#common_member_wechatmp to gain login access to an account via a plugin.php ac=wxregister request (the attacker does not have control over which account will be accessed).

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-20422?

It affects 1 product.


Products: Comsenz Discuzx.

## How do I fix CVE-2018-20422?

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

## Is CVE-2018-20422 being exploited?

There is no known exploitation of CVE-2018-20422 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2018-20423](https://insights.sbomify.com/CVE-2018-20423/): Auth bypass in n/a (high 8.1)
- [CVE-2018-20424](https://insights.sbomify.com/CVE-2018-20424/): Missing authorization in n/a (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-20422 and fix it if it is affected.

What it is: CVE-2018-20422 is a high-severity authentication bypass vulnerability in n/a, published on 24 Dec 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-20422 in the wild and no public exploit code.

Affected product: n/a. 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-2018-20422/ (Markdown: https://insights.sbomify.com/CVE-2018-20422/index.md)
```

## Sources

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

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