dbcve.org
Pricing TableWordPress extension · Pickplugins

CVE-2024-13469

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-28
Fix available
A fix is available. Upgrade to after 1.12.10 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
The Pricing Table by PickPlugins plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Button Link in all versions up to, and including, 1.12.10 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

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 Pricing Table by PickPlugins WordPress plugin fails to properly sanitize and escape the Button Link parameter, allowing authenticated users with Contributor-level access to inject malicious JavaScript that gets stored and executed when other users access affected pages.

MitigationUpdate the plugin to version 1.12.11 or later which contains the patched code, or implement proper input sanitization (e.g., esc_url()) and output escaping on the Button Link field.

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
Pricing TableWordPress extension
Affected:<= 1.12.10

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 plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Pricing Table by PickPlugins'. Note the installed version number shown below the plugin name.
    Affected if The plugin is installed and the version listed is 1.12.10 or lower
  2. Identify active pricing tables using Button Link
    Access your WordPress database or use a plugin editor to examine post content where pricing tables are stored. Look for posts with post_type 'pricing_table' or custom post types created by this plugin. Inspect the 'Button Link' or similar meta fields in the pricing table configuration.
    Affected if Any pricing table instances exist that have a URL configured in the Button Link field
  3. Examine Button Link content for injection payloads
    Review the actual value stored in the Button Link field for each pricing table. Look for patterns like 'javascript:', 'onclick=', 'onerror=', or other JavaScript protocol handlers that indicate stored XSS payload presence.
    Affected if The Button Link field contains URLs with 'javascript:' protocol or event handlers like onclick, onmouseover, or similar JavaScript injection patterns

A user is affected if the Pickplugins Pricing Table plugin version is 1.12.10 or lower AND at least one pricing table has a Button Link configured with a potentially malicious value.

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 a release after 1.12.10
Interim mitigation

Update the plugin to version 1.12.11 or later which contains the patched code, or implement proper input sanitization (e.g., esc_url()) and output escaping on the Button Link field.

Recommended fix Moderate confidence

1.12.11

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find 'Pricing Table by PickPlugins' in the plugin list
  4. Click 'Update now' if an update is available, or click 'Check for updates' and then update
  5. Verify the update completes successfully
  6. Confirm the plugin is now running version 1.12.11 or higher

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

Fix this in Pricing Table Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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