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

CVE-2025-62886

HIGH · 7.1 CVSS v3.1 Published 2025-10-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
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 wpdevart Pricing Table builder wpdevart-pricing-table allows Stored XSS.This issue affects Pricing Table builder: from n/a through <= 1.5.3.

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

A CSRF vulnerability in the wpdevart Pricing Table builder plugin (versions <=1.5.3) allows attackers to inject malicious scripts through stored XSS. By tricking an authenticated administrator into clicking a crafted link or visiting a malicious page, attackers can execute arbitrary JavaScript in the context of the admin session, potentially compromising the entire WordPress site.

MitigationUpdate to the latest version of the wpdevart Pricing Table builder plugin when available, and implement anti-CSRF tokens (nonces) on all form submissions and admin actions to prevent forged 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
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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. Verify wpdevart Pricing Table builder plugin is installed
    Log into WordPress admin, go to Plugins > Installed Plugins, and search for 'Pricing Table builder' by wpdevart. Confirm the plugin appears in the list.
    Affected if Plugin is present in the WordPress installation regardless of activation status
  2. Check plugin activation status
    In the same Plugins list, verify whether the wpdevart Pricing Table builder plugin is currently activated (look for 'Active' status indicator).
    Affected if Plugin is active
  3. Identify installed plugin version
    Click on the plugin in the Plugins list to view details, or access the main plugin file (typically in wp-content/plugins/pricing-table-builder/) and read the Version header in the plugin comments at the top of the main PHP file.
    Affected if Version number is 1.5.3 or lower
  4. Confirm vulnerability condition
    Compare your identified version against the affected range: versions 1.5.3 and below are vulnerable. If you cannot determine the exact version, treat any installation of this plugin at version 1.5.3 or lower as affected.
    Affected if Installed version is less than or equal to 1.5.3

You are affected if the wpdevart Pricing Table builder plugin is active and the installed version is 1.5.3 or lower.

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 to the latest version of the wpdevart Pricing Table builder plugin when available, and implement anti-CSRF tokens (nonces) on all form submissions and admin actions to prevent forged requests.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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