dbcve.org
Go PricingWordPress extension · Granthweb

CVE-2023-2494

HIGH · 8.8 CVSS v3.1 Published 2023-05-24
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 unauthorized modification of data due to a missing capability check on the 'process_postdata' function in versions up to, and including, 3.3.19. This makes it possible for authenticated attackers with a role that the administrator previously granted access to the plugin to modify access to the plugin when it should only be the administrator's privilege.

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 has a broken access control vulnerability where the 'process_postdata' function lacks a capability check, allowing any user with a role granted access to the plugin to modify plugin access settings that should be restricted to administrators only. This allows privilege escalation through unauthorized modification of access permissions.

MitigationUpdate the Go Pricing plugin to a version beyond 3.3.19. Until patched, review and restrict user roles granted access to the plugin settings to only trusted administrators.

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. Identify Go Pricing plugin version
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Go Pricing' (or 'Granthweb Go Pricing'). Check the version number displayed. Alternatively, check the plugin's main PHP file (usually /wp-content/plugins/go-pricing/ or similar path) for the version header in the plugin comments.
    Affected if The installed version is 3.3.19 or lower.
  2. Verify user role access to plugin settings
    Navigate to the Go Pricing settings page (usually under WP Admin > Go Pricing > Settings or similar). Look for access/permission settings that control which user roles can access or modify the plugin. Inspect which roles are granted access.
    Affected if Any user role other than Administrator (such as Editor, Author, Contributor, or Subscriber) is granted access to modify plugin settings.
  3. Inspect the process_postdata function capability
    Access the WordPress site via FTP or file manager. Locate the Go Pricing plugin main file containing the 'process_postdata' function (commonly in main plugin PHP file). Examine the function for capability checks (look for current_user_can, or similar permission functions).
    Affected if The 'process_postdata' function contains no capability check or allows any authenticated user with plugin access to execute it.
  4. Review role permission modifications
    Check user role capabilities in the database (wp_options table for roles) or use a role management plugin to compare current role capabilities against default WordPress roles. Look for any unauthorized changes to non-administrator role capabilities related to the plugin.
    Affected if Non-administrator roles have unexpected elevated capabilities (such as manage_options, edit_users, or plugin-specific capabilities) that were not intentionally assigned.

You are affected if the Go Pricing plugin version is 3.3.19 or lower AND any non-administrator user role has been granted access to modify plugin settings.

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

Update the Go Pricing plugin to a version beyond 3.3.19. Until patched, review and restrict user roles granted access to the plugin settings to only trusted administrators.

Fix this in Go Pricing Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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