dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2024-12771

HIGH · 8.8 CVSS v3.1 Published 2024-12-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The eCommerce Product Catalog Plugin for WordPress plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.3.43. This is due to missing or incorrect nonce validation on the 'customer_panel_password_reset' function. This makes it possible for unauthenticated attackers to reset the password of any administrator or customer account via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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

CSRF vulnerability in the WordPress eCommerce Product Catalog plugin where the 'customer_panel_password_reset' function lacks proper nonce validation, allowing unauthenticated attackers to forge password reset requests for any administrator or customer account by tricking a site administrator into clicking a malicious link.

MitigationUpdate the plugin to a version beyond 3.3.43 which includes proper nonce validation on the password reset function; until then, warn administrators not to click untrusted links and consider additional CSRF protections at the web application level.

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

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. Confirm plugin is installed
    Log into WordPress admin and navigate to Plugins > Installed Plugins, or inspect the wp-content/plugins directory for a folder containing 'ecommerce-product-catalog' or similar naming. Check if the eCommerce Product Catalog plugin appears in the list.
    Affected if The plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin, find the eCommerce Product Catalog entry in the Plugins list and note the version number displayed. Alternatively, open the main plugin PHP file (usually includes a version header) in wp-content/plugins/ecommerce-product-catalog/ or similar path.
    Affected if Version number displayed is 3.3.43 or lower, or version cannot be determined (assumed outdated)
  3. Verify customer_panel_password_reset functionality exists
    Inspect the plugin source code for the 'customer_panel_password_reset' function. In WordPress, this may be found in plugin PHP files under includes/user-functions.php or similar. Search for the function name to confirm it exists.
    Affected if The function 'customer_panel_password_reset' exists in the plugin code
  4. Check for nonce validation on password reset
    Locate the customer_panel_password_reset function in the plugin code and examine whether it includes nonce verification (look for wp_verify_nonce, check_admin_referer, or similar nonce validation calls) before processing the password reset request.
    Affected if The function lacks proper nonce validation (no wp_verify_nonce or check_admin_referer call found before processing)
  5. Confirm WordPress admin access
    Determine whether you have administrator-level access to the WordPress site. This is required to assess the full impact, as the CSRF targets administrators.
    Affected if You have admin access and the plugin is installed with the vulnerable function present

A user is affected if the WordPress eCommerce Product Catalog plugin is installed with version 3.3.43 or lower and contains the vulnerable customer_panel_password_reset function without nonce validation.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to a version beyond 3.3.43 which includes proper nonce validation on the password reset function; until then, warn administrators not to click untrusted links and consider additional CSRF protections at the web application level.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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