# CVE-2021-24800: DW Question & Answer Pro <= 1.3.4 - Arbitrary Comment Edition via IDOR

> An attacker can edit arbitrary comments belonging to other users due to missing ownership checks in the DW Question & Answer Pro plugin.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 25 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-q6xh-rw6q-pcc2

## What is CVE-2021-24800?

CVE-2021-24800 is a medium-severity missing authorization vulnerability in Unknown DW Question Answer Pro, published on 25 Apr 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The DW Question & Answer Pro WordPress plugin through 1.3.4 does not check that the comment to edit belongs to the user making the request, allowing any user to edit other comments.

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

## Which versions are affected by CVE-2021-24800?

It affects 1 product.


Products: Designwall Dw Question \& Answer.

## How do I fix CVE-2021-24800?

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

## Is CVE-2021-24800 being exploited?

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

## Other vulnerabilities in Unknown DW Question Answer Pro

- [CVE-2021-4408](https://insights.sbomify.com/CVE-2021-4408/): DW Question & Answer <= 1.5.8 - Cross-Site Request Forgery Bypass (medium 4.3)
- [CVE-2021-24805](https://insights.sbomify.com/CVE-2021-24805/): DW Question & Answer Pro <= 1.3.4 - Multiple CSRF (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-24800 and fix it if it is affected.

What it is: CVE-2021-24800 is a medium-severity missing authorization vulnerability in Unknown DW Question Answer Pro, published on 25 Apr 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-2021-24800 in the wild and no public exploit code.

Affected product: Unknown DW Question Answer Pro. 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-2021-24800/ (Markdown: https://insights.sbomify.com/CVE-2021-24800/index.md)
```

## Sources

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

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