# CVE-2022-3750: Ask Me < 6.8.7 - Post Deletion via CSRF

> Attackers can trick authenticated users into deleting posts without consent due to missing CSRF protection in the Ask Me plugin.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Nov 2022
- **Updated:** 30 Apr 2025
- **Also known as:** GHSA-vw43-4r8p-cvx6

## What is CVE-2022-3750?

CVE-2022-3750 is a medium-severity vulnerability in Unknown Ask me, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The  has a CSRF vulnerability that allows the deletion of a post without using a nonce or prompting for confirmation.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 1 product.


Products: Inkthemes Ask Me.

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

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

## Is CVE-2022-3750 being exploited?

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

## Other vulnerabilities in Unknown Ask me

- [CVE-2022-1251](https://insights.sbomify.com/CVE-2022-1251/): Ask Me < 6.8.4 - CSRF in Edit Profile (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3750 is a medium-severity vulnerability in Unknown Ask me, published on 21 Nov 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-3750 exists.

Affected product: Unknown Ask me. 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-3750/ (Markdown: https://insights.sbomify.com/CVE-2022-3750/index.md)
```

## Sources

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

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