dbcve.org
Woocommerce Thank You Page CustomizerWordPress extension · Villatheme

CVE-2022-46812

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 1.0.13 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
Cross-Site Request Forgery (CSRF) vulnerability in VillaTheme Thank You Page Customizer for WooCommerce – Increase Your Sales plugin <= 1.0.13 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 · high confidence

Cross-Site Request Forgery (CSRF) vulnerability in VillaTheme's Thank You Page Customizer for WooCommerce plugin (versions 1.0.13 and below). The plugin lacks proper nonce validation on state-changing actions, allowing attackers to trick authenticated administrators into performing unintended configuration changes via maliciously crafted requests.

MitigationImplement anti-CSRF tokens (nonce verification) on all form submissions and AJAX actions within the plugin, and verify the request origin using WordPress nonces and referer checks.

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
Woocommerce Thank You Page CustomizerWordPress extension
Affected:<= 1.0.13

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 plugin installation directory
    Access your WordPress site via FTP or file manager, navigate to /wp-content/plugins/ and look for a folder named 'woo-thank-you-page-customizer' or similar VillaTheme plugin directory.
    Affected if The plugin folder exists on the server.
  2. Identify the installed version number
    Check the main plugin file (usually namedwoo-thank-you-page-customizer.php or similar) inside the plugin folder for the version comment header, or access the WordPress admin dashboard under Plugins > Installed Plugins and locate 'WooCommerce Thank You Page Customizer' by VillaTheme to read the version number.
    Affected if Version 1.0.13 or lower is reported.
  3. Confirm plugin is active
    Log into WordPress admin, go to Plugins > Installed Plugins, and verify that WooCommerce Thank You Page Customizer is currently activated.
    Affected if The plugin shows as Active.
  4. Check for nonce validation in plugin code
    Examine the plugin PHP files for WordPress nonce verification calls (wp_verify_nonce, check_admin_referer, check_ajax_referer) on form processing and AJAX action handlers, particularly in files handling settings updates or state-changing operations.
    Affected if No nonce verification is found in the plugin code handling state-changing actions.
  5. Verify admin user sessions exist
    In WordPress admin under Users, confirm that administrator accounts exist and have access to the plugin settings pages.
    Affected if Active administrator users exist who can access the plugin configuration.

Your environment is affected if the VillaTheme WooCommerce Thank You Page Customizer plugin is installed at version 1.0.13 or below and is active, allowing authenticated administrators to be tricked into performing unintended configuration changes via malicious CSRF requests.

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 1.0.13
Interim mitigation

Implement anti-CSRF tokens (nonce verification) on all form submissions and AJAX actions within the plugin, and verify the request origin using WordPress nonces and referer checks.

Fix this in Woocommerce Thank You Page Customizer Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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