# CVE-2023-3869: wpDiscuz <= 7.6.3 - Insecure Direct Object Reference to Comment Rating Increase/Decrease

> Unauthenticated attackers can modify comment ratings in wpDiscuz due to missing authorization checks, requiring plugin updates.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 20 Oct 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-wvm9-mq8w-wrm8

## What is CVE-2023-3869?

CVE-2023-3869 is a medium-severity missing authorization vulnerability in advancedcoding Comments – wpDiscuz, published on 20 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The wpDiscuz plugin for WordPress is vulnerable to unauthorized modification of data due to a missing authorization check on the voteOnComment function in versions up to, and including, 7.6.3. This makes it possible for unauthenticated attackers to increase or decrease the rating of a comment.

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

## Which versions are affected by CVE-2023-3869?

It affects 1 product.


Products: Gvectors Wpdiscuz.

## How do I fix CVE-2023-3869?

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

## Is CVE-2023-3869 being exploited?

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

## Other vulnerabilities in advancedcoding Comments – wpDiscuz

- [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-2023-3869 and fix it if it is affected.

What it is: CVE-2023-3869 is a medium-severity missing authorization vulnerability in advancedcoding Comments – wpDiscuz, published on 20 Oct 2023. 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-2023-3869 in the wild and no public exploit code.

Affected product: advancedcoding Comments – wpDiscuz. 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-2023-3869/ (Markdown: https://insights.sbomify.com/CVE-2023-3869/index.md)
```

## Sources

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

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