dbcve.org
Price TableWordPress extension · Price Table Project

CVE-2022-25604

MEDIUM · 5.4 CVSS v3.1 Published 2022-03-18
Fix available
A fix is available. Upgrade to after 0.2.2 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
Authenticated (contributor of higher user role) Stored Cross-Site Scripting (XSS) vulnerability discovered in WordPress Price Table plugin (versions <= 0.2.2).

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

A stored XSS vulnerability in the WordPress Price Table plugin (versions <= 0.2.2) allows authenticated users with contributor-level or higher privileges to inject malicious JavaScript code through plugin input fields that aren't properly sanitized before being stored and rendered.

MitigationUpdate the Price Table plugin to the latest version available from the WordPress repository, or remove the plugin if no patched version exists. Review user role permissions as a secondary defense.

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
Price TableWordPress extension
Affected:<= 0.2.2

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. Check installed Price Table plugin version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins. Locate 'Price Table Project Price Table' and read the version number displayed below the plugin name. Alternatively, inspect the file /wp-content/plugins/price-table/includes/ or check the plugin's main PHP file for the 'Version' header in the plugin comment block.
    Affected if The displayed version number is 0.2.2 or lower (e.g., 0.2.2, 0.2.1, 0.1.0)
  2. Verify Price Table plugin is active
    In the WordPress admin > Plugins > Installed Plugins, check if 'Price Table Project Price Table' shows an 'Active' status or 'Deactivate' link under the plugin name.
    Affected if The plugin is currently active and running on the site
  3. Confirm presence of contributor-level or higher user accounts
    In WordPress admin > Users, review the list of registered users. Look for any accounts assigned the 'Contributor', 'Author', 'Editor', or 'Administrator' role.
    Affected if At least one user account exists with contributor-level permissions or higher, providing potential access to the vulnerable input fields
  4. Inspect plugin-stored data for unsanitized input
    Access the WordPress database (via phpMyAdmin or wp CLI) and query the options or postmeta tables for Price Table plugin records. Look for stored values in plugin-specific tables or the wp_options table with keys containing 'price_table' or similar. Examine the stored content for unescaped HTML script tags.
    Affected if Stored data contains raw HTML tags, script elements, or JavaScript code that appears unescaped in the database (e.g., <script> tags visible in plain text within the option/postmeta value)

Your environment is affected if the Price Table plugin version 0.2.2 or lower is installed and active on your WordPress site, especially when contributor-level or higher user accounts exist who could inject malicious scripts through plugin input fields.

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
Upgrade available Upgrade to a release after 0.2.2
Interim mitigation

Update the Price Table plugin to the latest version available from the WordPress repository, or remove the plugin if no patched version exists. Review user role permissions as a secondary defense.

Fix this in Price Table Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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