Go PricingWordPress extension · Granthweb
CVE-2023-2498
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 · uneditedThe Go Pricing - WordPress Responsive Pricing Tables plugin for WordPress is vulnerable to Stored Cross-Site Scripting via shortcodes in versions up to, and including, 3.3.19 due to insufficient input sanitization and output escaping. This makes it possible for contributor-level attackers 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 confidenceThe Go Pricing WordPress plugin fails to properly sanitize and escape input in its shortcode handlers, allowing contributor-level users to inject malicious JavaScript that gets stored and executes when other users view affected pricing table pages.
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
<= 3.3.19CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Go Pricing plugin is installedNavigate to WordPress admin > Plugins and look for 'Go Pricing' or 'Granthweb Go Pricing' in the installed plugins listAffected if The plugin appears in the installed plugins list
-
Check installed version numberIn WordPress admin > Plugins, click on the Go Pricing plugin to view its details, or check the plugin header in /wp-content/plugins/go-pricing/ includes/version.php or main plugin file for the version stringAffected if Version is 3.3.19 or lower
-
Verify contributor-level users can access shortcode functionalityIn WordPress admin, go to Users > Roles or check if contributors have permission to create/edit pages with shortcodes, or inspect the plugin role capabilities file for 'edit_posts' or 'publish_posts' permissionsAffected if Contributor role users can add or edit content containing shortcodes
-
Inspect pricing tables for suspicious shortcode contentCheck pricing table post types or custom post entries created with Go Pricing for unexpected attributes in [go_pricing] shortcodes, or query wp_posts table for post_type 'go_pricing' and examine post_content for encoded or unusual parametersAffected if Pricing tables contain shortcodes with encoded JavaScript, event handlers (onclick, onerror, etc.), or unexpected attribute values
You are affected if the Go Pricing plugin version is 3.3.19 or lower AND contributor-level users can add or edit content containing shortcodes, as the stored XSS can be injected and execute when others view the pricing tables.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a version newer than 3.3.19 which contains proper input sanitization and output escaping. If no update is available, restrict shortcode usage permissions to administrator-level only or implement custom input filtering.
Fix this in Go Pricing
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2498 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2498 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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