dbcve.org
Th Advance Product SearchWordPress extension · Themehunk

CVE-2022-38057

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-25
Fix available
A fix is available. Upgrade to 1.2.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

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

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Missing Authorization vulnerability in the ThemeHunk Advance WordPress Search Plugin version 1.2.1 and below allows unauthorized users to access privileged functionality. The plugin fails to implement proper capability checks or nonce validation on certain actions, enabling attackers to bypass authorization controls.

MitigationUpdate to the latest version of the plugin once a patched release is available. Until then, restrict administrator access to the plugin settings and monitor for suspicious activity.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Th Advance Product SearchWordPress extension
Affected:< 1.2.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the ThemeHunk plugin in your WordPress installation
    Check your wp-content/plugins/ directory for a folder named 'advance-product-search', 'th-advance-product-search', or similar ThemeHunk search-related plugin folder. Alternatively, log into WordPress admin and navigate to Plugins to find the plugin.
    Affected if The plugin folder exists in the plugins directory or appears in the WordPress admin plugins list
  2. Identify the installed version number
    Open the main plugin PHP file (usually named advance-product-search.php or similar) and look for the version comment in the file header, or check the readme.txt file for the 'Stable tag' version entry.
    Affected if The version shown is 1.2.1 or any version below 1.2.2
  3. Verify the vulnerability is exploitable
    Since the flaw is in missing capability checks and nonce validation on certain actions, the mere presence of the vulnerable plugin version means unauthorized users could access privileged functionality if they can reach the WordPress site.
    Affected if The plugin is active on the site and running version 1.2.1 or below

You are affected if the ThemeHunk Advance WordPress Search plugin is installed and active at a version below 1.2.2.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.2 or later
Fixed in 1.2.2
Interim mitigation

Update to the latest version of the plugin once a patched release is available. Until then, restrict administrator access to the plugin settings and monitor for suspicious activity.

Recommended fix High confidence

1.2.2

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Th Advance Product Search' or 'Advance WordPress Search Plugin'
  4. Check if the current version is below 1.2.2
  5. If vulnerable, click 'Update Now' to update to the latest version
  6. Alternatively, download version 1.2.2 from the WordPress plugin repository or ThemeHunk and upload manually
  7. After updating, verify the plugin version shows 1.2.2 or higher
  8. Review any user accounts or settings that may have been created during the vulnerability period

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Th Advance Product Search Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38057 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38057 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data