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

CVE-2025-48342

MEDIUM · 5.4 CVSS v3.1 Published 2025-05-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
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 RedefiningTheWeb Dynamic Pricing & Discounts Lite for WooCommerce woo-dynamic-pricing-discounts-lite allows Cross Site Request Forgery.This issue affects Dynamic Pricing & Discounts Lite for WooCommerce: from n/a through <= 2.0.4.

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

Cross-Site Request Forgery (CSRF) vulnerability in the Dynamic Pricing & Discounts Lite for WooCommerce plugin allows attackers to potentially trick authenticated administrators into performing unintended actions such as modifying pricing rules or discount configurations via forged requests.

MitigationImplement WordPress nonces (anti-CSRF tokens) on all state-changing forms and AJAX actions within the plugin to verify the authenticity of requests.

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
None
Integrity
Low
Availability
Low

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

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
    Check your WordPress installation at wp-content/plugins/ for a folder named 'dynamic-pricing-lite' or similar variants of 'dynamic-pricing-discounts-lite-for-woocommerce'.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Identify the installed version
    Open the main plugin PHP file (usually named main.php, index.php, or the plugin root file) and look for a version comment or 'Version:' header in the plugin file headers. Alternatively, check the WordPress plugin admin page for the installed version number.
    Affected if A version number is displayed and matches any known vulnerable release of this plugin.
  3. Inspect admin form handlers for nonce verification
    Examine PHP files in the plugin directory that handle admin form submissions (typically files with 'admin', 'settings', 'pricing', 'discount' in the name). Search for 'wp_nonce_field', 'wp_nonce', 'verify_nonce', or 'check_admin_referer' function calls within form handling code.
    Affected if State-changing admin forms (pricing rules, discount configurations) lack nonce verification calls.
  4. Inspect AJAX action handlers for nonce verification
    Search plugin PHP files for 'add_action' calls registering AJAX handlers (look for 'wp_ajax_' hooks). For each AJAX handler found, verify that nonce verification is performed using 'check_ajax_referer' or 'wp_verify_nonce' before processing the request.
    Affected if AJAX endpoints that modify pricing or discount settings do not verify nonces before executing state-changing operations.
  5. Review nonce implementation in configuration files
    Locate files handling pricing rules and discount configuration (typically files named like 'class-pricing.php', 'class-discounts.php', 'settings.php', or 'admin-options.php'). Verify that each form and AJAX action that modifies settings includes nonce field generation and verification.
    Affected if Configuration files that save pricing rules or discount settings do not implement WordPress nonce validation.

Your environment is affected if the Dynamic Pricing & Discounts Lite for WooCommerce plugin is installed and its admin forms or AJAX actions handling pricing rules and discount configurations lack WordPress nonce verification.

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

Implement WordPress nonces (anti-CSRF tokens) on all state-changing forms and AJAX actions within the plugin to verify the authenticity of requests.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,290
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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