# CVE-2022-36296: WordPress ActiveDEMAND plugin <= 0.2.27 - Broken Authentication vulnerability

> Unauthenticated attackers can update, create, or delete posts in the ActiveDEMAND WordPress plugin due to broken authentication.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Aug 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-mp4f-pwv2-xxc8

## What is CVE-2022-36296?

CVE-2022-36296 is a medium-severity authentication bypass vulnerability in JumpDEMAND Inc. ActiveDEMAND, published on 5 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Broken Authentication vulnerability in JumpDEMAND Inc. ActiveDEMAND plugin <= 0.2.27 at WordPress allows unauthenticated post update/create/delete.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Jumpdemand Activedemand.

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

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

## Is CVE-2022-36296 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36296 is a medium-severity authentication bypass vulnerability in JumpDEMAND Inc. ActiveDEMAND, published on 5 Aug 2022. 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-2022-36296 in the wild and no public exploit code.

Affected product: JumpDEMAND Inc. ActiveDEMAND. 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-36296/ (Markdown: https://insights.sbomify.com/CVE-2022-36296/index.md)
```

## Sources

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

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