# CVE-2022-43492: WordPress Comments – wpDiscuz plugin 7.4.2 - Auth. Insecure Direct Object References (IDOR) vulnerability

> Authenticated subscribers can access or modify other users' comments due to insecure direct object references in the wpDiscuz plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-vcj3-36cm-3c25

## What is CVE-2022-43492?

CVE-2022-43492 is a medium-severity missing authorization vulnerability in gVectors Team Comments – wpDiscuz (WordPress plugin), published on 18 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Auth. (subscriber+) Insecure Direct Object References (IDOR) vulnerability in Comments – wpDiscuz plugin 7.4.2 on WordPress.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2022-43492?

It affects 1 product.


Products: Gvectors Wpdiscuz.

## How do I fix CVE-2022-43492?

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

## Is CVE-2022-43492 being exploited?

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

## Other vulnerabilities in gVectors Team Comments – wpDiscuz (WordPress plugin)

- [CVE-2020-24186](https://insights.sbomify.com/CVE-2020-24186/): File upload in n/a (critical 10.0)
- [CVE-2024-9488](https://insights.sbomify.com/CVE-2024-9488/): Comments – wpDiscuz <= 7.6.24 - Authentication Bypass via WordPress.com OAuth provider (critical 9.8)
- [CVE-2020-13640](https://insights.sbomify.com/CVE-2020-13640/): SQL injection in n/a (critical 9.8)
- [CVE-2026-22193](https://insights.sbomify.com/CVE-2026-22193/): wpDiscuz before 7.6.47 - SQL Injection in getAllSubscriptions() (critical 9.2)
- [CVE-2026-22192](https://insights.sbomify.com/CVE-2026-22192/): Voltronic Power SNMP Web Pro 1.1 Authentication Bypass via localStorage (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-43492 and fix it if it is affected.

What it is: CVE-2022-43492 is a medium-severity missing authorization vulnerability in gVectors Team Comments – wpDiscuz (WordPress plugin), published on 18 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-43492 in the wild and no public exploit code.

Affected product: gVectors Team Comments – wpDiscuz (WordPress plugin). 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-2022-43492/ (Markdown: https://insights.sbomify.com/CVE-2022-43492/index.md)
```

## Sources

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

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