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

CVE-2026-1852

MEDIUM · 6.1 CVSS v3.1 Published 2026-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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
The Product Pricing Table by WooBeWoo plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.1.0. This is due to missing or incorrect nonce validation on the updateLabel() and remove() functions. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages or delete pricing tables 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

The Product Pricing Table by WooBeWoo plugin for WordPress versions up to 1.1.0 lacks proper nonce validation in the updateLabel() and remove() functions, allowing unauthenticated attackers to forge administrative requests via CSRF. Attackers can inject malicious scripts through the updateLabel function or delete pricing tables through the remove function by tricking administrators into clicking crafted links.

MitigationImplement WordPress nonce verification (wp_verify_nonce) in both updateLabel() and remove() functions, and add nonce fields (wp_nonce_field) to all relevant admin forms and AJAX handlers to prevent CSRF exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm the plugin is installed
    Check your WordPress installation's wp-content/plugins/ directory for a folder named 'product-pricing-table-by-woobewwoo' or similar variant (also check 'product-pricing-table-by-woobewoo'). Alternatively, look in wp-admin > Plugins for 'Product Pricing Table by WooBeWwoo' or 'Product Pricing Table by WooBeWoo'.
    Affected if The plugin is not present in the WordPress installation.
  2. Identify the installed version
    If the plugin is found, open the main plugin PHP file (usually named plugin-name.php) and look for the 'Version:' header in the plugin comment block at the top. Alternatively, check in wp-admin > Plugins > Plugin Details for the version number.
    Affected if Version 1.1.0 or any earlier version is installed.
  3. Locate the vulnerable functions
    In the plugin directory, search for PHP files containing 'function updateLabel' and 'function remove'. These are typically found in the main plugin file or an admin/class file.
    Affected if Both updateLabel() and remove() functions exist in the plugin code.
  4. Verify missing nonce validation
    Open the PHP files containing updateLabel() and remove() functions. Examine each function for the presence of 'wp_verify_nonce' or 'check_admin_referer' calls at the function entry point. Also check for 'wp_nonce_field' or 'wp_create_nonce' in related AJAX handlers or form outputs.
    Affected if No nonce verification is present at the start of either updateLabel() or remove() functions, or no nonce fields are added to forms calling these functions.

You are affected if the Product Pricing Table by WooBeWoo plugin is installed with version 1.1.0 or earlier AND the updateLabel() and remove() functions lack wp_verify_nonce or check_admin_referer 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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement WordPress nonce verification (wp_verify_nonce) in both updateLabel() and remove() functions, and add nonce fields (wp_nonce_field) to all relevant admin forms and AJAX handlers to prevent CSRF exploitation.

Recommended fix Moderate confidence

Version greater than 1.1.0 (check WordPress plugin repository for latest stable release)

  1. Check the WordPress admin dashboard for the Product Pricing Table by WooBeWoo plugin version under Plugins > Installed Plugins
  2. If the installed version is 1.1.0 or below, navigate to Plugins > Add New > Upload Plugin to upload and install an updated version when available
  3. Alternatively, go to Plugins > Add New and search for 'Product Pricing Table by WooBeWoo' to install any newer version that addresses the CSRF vulnerability
  4. After updating, verify the new version under Plugins > Installed Plugins
  5. Ensure WordPress core and all other plugins are kept up to date as a security best practice
  6. Review the plugin's settings after upgrade to confirm pricing tables are intact and functioning

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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