Pricing Table By SupsysticWordPress extension · Supsystic
CVE-2020-9394
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 · uneditedAn issue was discovered in the pricing-table-by-supsystic plugin before 1.8.2 for WordPress. It allows CSRF.
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 confidenceCross-Site Request Forgery vulnerability in the pricing-table-by-supsystic WordPress plugin before version 1.8.2. Attackers can potentially trick authenticated administrators into performing unintended actions (such as modifying plugin settings or price table configurations) by forging requests from malicious 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
Pricing Table By SupsysticWordPress extension
< 1.8.2CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify the plugin is installedCheck if the pricing-table-by-supsystic plugin exists in your WordPress installation by navigating to /wp-content/plugins/ or checking the Plugins page in the WordPress admin dashboard.Affected if The plugin is present in the plugins directory or listed in WordPress admin.
-
Identify the installed versionIn WordPress admin, go to Plugins > Pricing Table by Supsystic and check the version number displayed, or inspect the main plugin file (typically pricing-table-by-supsystic.php) to find the 'Version' header comment.Affected if The version displayed is below 1.8.2 (e.g., 1.8.1, 1.8.0, 1.7.x, etc.).
-
Confirm the plugin is activeCheck the Plugins page in WordPress admin to verify whether Pricing Table by Supsystic is currently activated. An inactive plugin poses no CSRF risk since no authenticated admin session interacts with it.Affected if The plugin is both installed AND activated.
-
Review plugin settings for unauthorized changesNavigate to the plugin settings page (Pricing Table > Settings or similar) and inspect all configuration options for unexpected modifications, particularly nonce validation settings, admin action endpoints, or any price table configurations that could have been altered via forged requests.Affected if Settings appear modified, contain unexpected values, or include requests to external domains that you did not intentionally configure.
You are affected if the pricing-table-by-supsystic plugin is installed, active, and running a version earlier than 1.8.2.
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 data1.8.2
Update the pricing-table-by-supsystic plugin to version 1.8.2 or later to obtain the CSRF fix. Until then, restrict administrative access and monitor for suspicious admin actions.
Fix this in Pricing Table By Supsystic
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-2020-9394 — 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-2020-9394 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