# CVE-2022-38057: WordPress TH Advance Product Search plugin <= 1.2.1 - Unauthenticated Plugin Settings Reset vulnerability

> Unauthenticated attackers can reset plugin settings due to missing authorization checks in the Advance WordPress Search plugin.

- **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:** 25 Mar 2024
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-prx3-7v7j-286r

## What is CVE-2022-38057?

CVE-2022-38057 is a medium-severity missing authorization vulnerability in ThemeHunk Advance WordPress Search Plugin, published on 25 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authorization vulnerability in ThemeHunk Advance WordPress Search Plugin.This issue affects Advance WordPress Search Plugin: from n/a through 1.2.1.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Themehunk Th Advance Product Search.

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

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

## Is CVE-2022-38057 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38057 is a medium-severity missing authorization vulnerability in ThemeHunk Advance WordPress Search Plugin, published on 25 Mar 2024. 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-38057 in the wild and no public exploit code.

Affected product: ThemeHunk Advance WordPress Search Plugin. 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-38057/ (Markdown: https://insights.sbomify.com/CVE-2022-38057/index.md)
```

## Sources

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

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