dbcve.org
Minimum Purchase For WoocommerceWordPress extension · Varktech

CVE-2023-30492

MEDIUM · 5.4 CVSS v3.1 Published 2023-10-26
Fix available
A fix is available. Upgrade to after 2.0.0.1 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in Vark Minimum Purchase for WooCommerce plugin <= 2.0.0.1 versions.

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

An authenticated stored Cross-Site Scripting (XSS) vulnerability exists in the Vark Minimum Purchase for WooCommerce plugin for versions up to and including 2.0.0.1. Users with contributor-level access or higher can inject malicious JavaScript code into plugin settings or fields, which is then stored and executed when other users view the affected pages.

MitigationUpdate the Vark Minimum Purchase for WooCommerce plugin to a version beyond 2.0.0.1 when available. Until then, restrict contributor-level access and sanitize any user inputs in the plugin.

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
Minimum Purchase For WoocommerceWordPress extension
Affected:<= 2.0.0.1

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Verify the plugin is installed
    Check for the plugin directory in wp-content/plugins, looking for folders named 'varktech-minimum-purchase-for-woocommerce' or similar Varktech Minimum Purchase variants
    Affected if The plugin directory exists in the WordPress plugins folder
  2. Determine installed plugin version
    Read the main plugin file header (usually varktech-minimum-purchase-for-woocommerce.php) to find the Version field, or check the WordPress plugin admin page for the installed version number
    Affected if The reported version is 2.0.0.1 or lower
  3. Check for untrusted user accounts with contributor access
    In WordPress admin, go to Users > All Users and review the role column for accounts that have contributor-level or higher privileges that are not trusted administrators
    Affected if There are users with contributor, author, editor, or administrator roles who should not have write access to plugin settings
  4. Inspect plugin settings pages for unsanitized inputs
    Navigate to the plugin settings pages in WooCommerce > Minimum Purchase and examine whether input fields accept raw HTML or script tags without encoding
    Affected if The plugin settings fields accept and store raw HTML or JavaScript without sanitization
  5. Review stored plugin data in database
    Query the wp_postmeta or wp_options table for entries related to the plugin (vtprd, varktech, minimum purchase) and check if stored values contain unescaped script tags or HTML
    Affected if Stored plugin configuration data contains raw HTML or script elements

A user is affected if the Varktech Minimum Purchase for WooCommerce plugin version 2.0.0.1 or lower is installed AND untrusted users with contributor-level or higher access exist on the site who could inject malicious scripts into plugin settings.

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.

From vendor data
Upgrade available Upgrade to a release after 2.0.0.1
Interim mitigation

Update the Vark Minimum Purchase for WooCommerce plugin to a version beyond 2.0.0.1 when available. Until then, restrict contributor-level access and sanitize any user inputs in the plugin.

Fix this in Minimum Purchase For Woocommerce Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-30492 — 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-2023-30492 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