Data Tables GeneratorWordPress extension · Supsystic
CVE-2020-12076
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 data-tables-generator-by-supsystic plugin before 1.9.92 for WordPress lacks CSRF nonce checks for AJAX actions. One consequence of this is stored XSS.
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 data-tables-generator-by-supsystic WordPress plugin before version 1.9.92 fails to implement CSRF nonce verification on AJAX actions. This missing protection allows attackers to craft malicious requests that execute arbitrary JavaScript in the context of the affected site, resulting in stored cross-site scripting (XSS) that can compromise admin sessions or inject malicious content.
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
Data Tables GeneratorWordPress extension
< 1.9.92CVSS 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.
-
Check if Data Tables Generator plugin is installedNavigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'Data Tables Generator by Supsystic' or check the /wp-content/plugins/table-generator-by-supsystic directory existenceAffected if Plugin is not found in the WordPress installation
-
Determine installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins > Data Tables Generator by Supsystic and read the version number displayed, or inspect the plugin's main PHP file header for 'Version:' tagAffected if Version is below 1.9.92 (e.g., 1.9.91, 1.9.90, etc.)
-
Verify AJAX actions lack nonce verificationInspect the plugin's AJAX handler PHP files in /wp-content/plugins/table-generator-by-supsystic/ for 'add_action("wp_ajax_' calls and check if they include nonce verification using 'check_ajax_referer' or 'wp_verify_nonce' before processing requestsAffected if AJAX actions process requests without calling nonce verification functions (vulnerable code pattern)
User is affected if the Data Tables Generator by Supsystic plugin is installed with a version lower than 1.9.92, as the missing CSRF nonce validation on AJAX endpoints enables stored XSS attacks.
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.9.92
Update the data-tables-generator-by-supsystic plugin to version 1.9.92 or later to include proper CSRF nonce validation on AJAX endpoints.
Fix this in Data Tables Generator
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-12076 — 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-12076 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