dbcve.org
Responsive Pricing TableWordPress extension · Wpdarko

CVE-2022-46855

MEDIUM · 5.4 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 5.1.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in WP Darko Responsive Pricing Table plugin <= 5.1.6 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

Stored Cross-Site Scripting (XSS) vulnerability in the WP Darko Responsive Pricing Table plugin allows authenticated users with contributor-level permissions or higher to inject malicious JavaScript through plugin settings or pricing table configurations, which executes when other users view the affected pricing tables.

MitigationUpdate the plugin to a version newer than 5.1.6. If no update is available, consider removing the plugin until a patch is released.

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
Responsive Pricing TableWordPress extension
Affected:< 5.1.7

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Verify the plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Wpdarko Responsive Pricing Table' or 'Responsive Pricing Table' in the list of active plugins.
    Affected if The plugin appears in the installed plugins list and is activated.
  2. Check the installed version
    In Plugins list, click on the plugin name or view its details to read the Version number. Alternatively, inspect the main plugin file (typically wp-content/plugins/responsive-pricing-table/main.php or similar) and look for the 'Version' header comment.
    Affected if The version number shown is less than 5.1.7 (for example, 5.1.6, 5.0.0, etc.).
  3. Identify existing pricing table configurations
    Look for a menu item labeled 'Pricing Table', 'RP Pricing Tables', or similar in the WordPress admin sidebar. Click through to list any pricing tables that have been created.
    Affected if One or more pricing tables exist in the system, meaning configurations have been saved to the database.
  4. Inspect pricing table settings for script injection
    Access each pricing table configuration and examine fields such as table title, plan name, price, features list, button text, and custom CSS/JS fields. Check for unexpected <script> tags, javascript: URLs, event handlers (onclick, onerror, onload), or encoded payloads.
    Affected if Any field contains raw HTML script tags or JavaScript event handlers that were not intentionally added by an administrator.
  5. Review user accounts with contributor or higher access
    In WordPress admin, go to Users and review the role assigned to each user. Identify any users with Contributor, Author, Editor, or Administrator roles.
    Affected if There are multiple users with contributor-level or higher permissions, any of whom could have exploited this vulnerability.

The environment is affected if the WP Darko Responsive Pricing Table plugin version is below 5.1.7 and at least one pricing table configuration exists in the database, regardless of whether malicious code is currently visible.

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
Upgrade available Upgrade to 5.1.7 or later
Fixed in 5.1.7
Interim mitigation

Update the plugin to a version newer than 5.1.6. If no update is available, consider removing the plugin until a patch is released.

Recommended fix High confidence

Responsive Pricing Table version 5.1.7

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate 'Responsive Pricing Table' by WP Darko
  4. Click 'Update Now' if an update is available, or manually download version 5.1.7 from the WordPress plugin repository
  5. Verify the plugin updated successfully to version 5.1.7

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

Fix this in Responsive Pricing Table 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 the upgrade done

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-2022-46855 — 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-46855 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