dbcve.org
Go PricingWordPress extension · Granthweb

CVE-2023-2500

HIGH · 8.8 CVSS v3.1 Published 2023-05-25
Fix available
A fix is available. Upgrade to after 3.3.19 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Go Pricing - WordPress Responsive Pricing Tables plugin for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 3.3.19 via deserialization of untrusted input from the 'go_pricing' shortcode 'data' parameter. This allows authenticated attackers, with subscriber-level permissions and above, to inject a PHP Object. No POP chain is present in the vulnerable plugin. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 Go Pricing WordPress plugin up to version 3.3.19 is vulnerable to PHP Object Injection via insecure deserialization of the 'data' parameter in the 'go_pricing' shortcode. Authenticated attackers with subscriber-level permissions or higher can inject arbitrary PHP objects. While no POP chain exists within the plugin itself, the vulnerability could be weaponized if other installed plugins or themes provide a POP chain, enabling arbitrary file deletion, data exfiltration, or code execution.

MitigationUpdate the Go Pricing plugin to version 3.3.20 or later, which replaces insecure PHP deserialization with JSON-based data handling. Until patched, ensure only trusted users have contributor-level or higher access and consider removing the plugin if a POP chain exists elsewhere on the site.

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
Go PricingWordPress extension
Affected:<= 3.3.19

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 Go Pricing plugin version
    Access WordPress admin > Plugins > Installed Plugins and locate 'Go Pricing' or inspect the plugin header file (e.g., go_pricing.php) for the 'Version' comment
    Affected if Version is 3.3.19 or lower
  2. Identify go_pricing shortcode usage
    Search WordPress database or content files for '[go_pricing]' shortcode usage in posts, pages, or widgets
    Affected if The shortcode is actively used on the site
  3. Verify authenticated user roles exist
    Navigate to WordPress admin > Users and review existing user accounts for roles at Subscriber level or higher (Subscriber, Contributor, Author, Editor, Administrator)
    Affected if Any user account with Subscriber role or above exists
  4. Audit other plugins for POP chain potential
    Review installed plugins and themes for code containing unserialize() calls that could be chained with the object injection, or use a security scanner to identify deserialization sinks
    Affected if Vulnerable plugin version AND other plugins/themes provide a POP chain

You are affected if the Go Pricing plugin version is 3.3.19 or lower AND the go_pricing shortcode is in use AND any authenticated user with subscriber-level access exists, especially if other plugins provide a POP chain for exploitation.

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 3.3.19
Interim mitigation

Update the Go Pricing plugin to version 3.3.20 or later, which replaces insecure PHP deserialization with JSON-based data handling. Until patched, ensure only trusted users have contributor-level or higher access and consider removing the plugin if a POP chain exists elsewhere on the site.

Recommended fix Moderate confidence

latest available version (newer than 3.3.19)

  1. 1. Back up the WordPress site database and files before making any changes.
  2. 2. Check for any available updates to the Go Pricing plugin through WordPress admin > Plugins > All Plugins.
  3. 3. If an update is available, update the Go Pricing plugin to the latest version.
  4. 4. Verify the update was successful and the new version is installed.
  5. 5. Review user roles and permissions on the site to ensure no unnecessary subscriber-level accounts exist.
  6. 6. If no update is available from the WordPress repository, consider alternative pricing table plugins or contact the vendor directly for a patched version.

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

Fix this in Go Pricing 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-2023-2500 — 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-2023-2500 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