# CVE-2022-3082: miniOrange Discord Integration < 2.1.6 - Subscriber+ App Disabling

> Any logged-in user can disable the Discord integration app due to missing authorization and CSRF checks in AJAX actions.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **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:** 17 Oct 2022
- **Updated:** 13 May 2025
- **Also known as:** GHSA-3p65-3mvv-fjcq

## What is CVE-2022-3082?

CVE-2022-3082 is a medium-severity missing authorization vulnerability in Unknown miniOrange Discord Integration, published on 17 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The miniOrange Discord Integration WordPress plugin before 2.1.6 does not have authorisation and CSRF in some of its AJAX actions, allowing any logged in users, such as subscriber to call them, and disable the app for example

Weakness: CWE-862 (Missing Authorization), CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Miniorange Discord Integration.

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

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

## Is CVE-2022-3082 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3082 is a medium-severity missing authorization vulnerability in Unknown miniOrange Discord Integration, published on 17 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3082 exists.

Affected product: Unknown miniOrange Discord Integration. 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-3082/ (Markdown: https://insights.sbomify.com/CVE-2022-3082/index.md)
```

## Sources

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

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