# CVE-2022-1749: WPMK Ajax Finder <= 1.0.1 - Cross-Site Request Forgery to Cross-Site Scripting

> Attackers can exploit missing nonce checks to inject arbitrary scripts via CSRF, potentially leading to code execution in the WPMK Ajax Finder plugin.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 13 Jun 2022
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-8m25-j5jf-5mj2

## What is CVE-2022-1749?

CVE-2022-1749 is a high-severity vulnerability in createplugin WPMK Ajax Finder, published on 13 Jun 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 WPMK Ajax Finder WordPress plugin is vulnerable to Cross-Site Request Forgery via the createplugin_atf_admin_setting_page() function found in the ~/inc/config/create-plugin-config.php file due to a missing nonce check which allows attackers to inject arbitrary web scripts, in versions up to and including 1.0.1.

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

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

It affects 1 product.


Products: Wpmk Ajax Finder Project Wpmk Ajax Finder.

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

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

## Is CVE-2022-1749 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1749 is a high-severity vulnerability in createplugin WPMK Ajax Finder, published on 13 Jun 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-1749 exists.

Affected product: createplugin WPMK Ajax Finder. 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-1749/ (Markdown: https://insights.sbomify.com/CVE-2022-1749/index.md)
```

## Sources

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

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